adminsso — Reseller API
Create the caller reseller administrator login link through the Reseller API, with request fields, response details, errors and cURL/Python/PHP examples.
/api/v1/adminsso/Also accepts GETGenerates a signed quick-login URL for the authenticated reseller itself. There is no operation-specific user parameter: the target is taken from X-RESELLER after authentication. This logs into RAPP on HTTPS port 4444, not the root WAP panel. The token generator sets a 30-minute expiry. Treat the complete URL as a credential and do not log it, include it in analytics or follow it automatically in a backend test. The routed endpoint is adminsso; the internal handler name wapsso and its older source comment are not a public wapsso route.
Request
| Property | Value |
|---|---|
| Methods | GET, POST |
| Versioned path | /api/v1/adminsso/ |
| Default path | /api/adminsso/ |
| Authentication | Reseller API credentials. |
| Header | Required value |
|---|---|
X-RESELLER | The reseller account owning these API credentials. |
X-API-USER | Your Reseller API username. |
X-API-PASSWORD | Its API password. |
No endpoint-specific query or body fields are required.
Replace server.example.com, examplereseller, billing_api and YOUR_API_PASSWORD in each standalone example. Replace operation sample values with your actual target and an existing package where required. Python needs Requests; PHP needs the cURL extension. These examples make real calls when run.
Success response
HTTP 200. Illustrative values; account records and server values vary. Stored account examples show only selected fields.
{
"data": {
"url": "https://server.example.com:4444/quick/EXAMPLE_TOKEN"
},
"info": "SSO Login Url of Admin",
"status": 200
}| Field | Type | Meaning |
|---|---|---|
status | integer | 200 on the documented success branch. |
info | string | Operation description. |
data | object | Operation data described below. |
data.url | string | Signed quick-login URL; its token is a credential. |
Errors and demo mode
| Condition | Actual HTTP status | Response behavior |
|---|---|---|
| Missing credentials with no other authenticated identity | 403 | detail: Authentication credentials were not provided. |
| Rejected password or source IP | 403 | detail: Invalid API credentials |
| Demo server | 400 | error: Demo server; info: Api Operations not available in demo server; JSON status: 403. |
| Quick-login helper returns no URL | Server error | The current failure branch references an undefined variable; a normal operation JSON error is not guaranteed. |
| Unsupported method | 405 after authentication | Method-not-allowed response. |
Check both the HTTP status and JSON shape. Authentication failures do not use the operation envelope. Unexpected uncaught server errors are not guaranteed to return the documented JSON shape. Do not automatically retry account creation, password changes, deletions or SSO generation after a timeout: confirm the actual state first.
See Reseller API authentication and connection troubleshooting.