Reseller API — Account and Subreseller Integrations
Use the Eenos Reseller API with reseller-scoped credentials, ownership checks, provisioning, SSO and account usage operations.
The Reseller API serves integrations for one Eenos reseller and its permitted accounts. It is also known as the alpha/chain reseller API. Its credentials are created in RAPP → Eenos → API → API Manager, separately from WAP API credentials and the reseller panel password.
Base URLs
| URL | Meaning |
|---|---|
https://server.example.com:4444/api/ | Default reseller API routes. |
https://server.example.com:4444/api/v1/ | Explicit v1 routes used by this reference. |
Use the server HTTPS hostname and a valid certificate. Port 4444 is RAPP; sending these credentials to WAP port 5555 does not select the reseller API. Both base paths currently route to the installed reseller v1 handlers.
Authentication headers
Send all three headers on every request:
| Header | Value |
|---|---|
X-RESELLER | The reseller hosting username that owns the API user. |
X-API-USER | The API username created within that reseller. |
X-API-PASSWORD | That API user's password. |
The reseller identifier accepts 1–32 ASCII letters, digits, underscores or hyphens. Authentication requires an existing reseller record, an API-user record for that reseller, a matching password hash and any configured source-IP restriction. The reseller identity comes from this authenticated context, not a body field. Unlike the WAP legacy interface, this authenticator does not use body/query apiuser or apiauth credentials.
Restricted access compares the detected client IP with the saved individual addresses. The backend takes the first X-Forwarded-For value when present, otherwise REMOTE_ADDR. A trusted proxy must replace untrusted forwarding headers; use the address actually observed by the panel when configuring an allowlist.
Use dedicated backend credentials and the API Manager guide for creation, rotation and revocation. API Manager does not offer per-operation permission scopes. Do not expose these credentials in browser JavaScript.
Ownership and reseller limits
Account-targeting operations check membership in the authenticated reseller configuration's accounts list and require the hosting-user record. Do not assume a matching username or a nested reseller hierarchy grants access to an account absent from that list. Package selection in creation and package changes additionally checks the package owner.
Some changes reject suspended target accounts; each operation documents its state requirements. Subreseller creation/promotion depends on chain-reselling settings and available account limits. Under a finite parent limit, a subreseller account allocation must be strictly less than the remaining allocation; unlimited cannot be assigned by a finite parent. Check the operation-specific rules rather than assuming all root API options are available.
List/count operations read the reseller's account list, so a self-owned reseller may appear when listed there. These are not global server account lists. Load/version endpoints provide authenticated server information.
Request and response conventions
All 25 operations accept GET and POST. POST reads JSON/form data; GET reads query parameters. The examples use form-encoded POST and keep credentials in headers. Use POST for mutations and SSO generation.
Operation success usually returns data, info and numeric status 200. Read the actual HTTP status as well: validation/ownership failures return HTTP 400 with JSON status 400, while backend failures commonly return HTTP 400 with JSON status 500. Demo-wrapped operations return HTTP 400 with JSON status 403. Load/version and the API-root login do not use that demo wrapper.
Missing credentials without another authenticated identity return HTTP 403 with a detail message; rejected passwords or source IPs return HTTP 403 with detail Invalid API credentials. Incomplete or malformed reseller header sets do not establish an API identity. Other configured session/token authentication can affect browser requests; use an independent client without panel cookies to test API headers.
The API-root login returns reseller, username and the string auth="None" for header authentication. It does not issue a bearer token. adminsso generates a login link for the authenticated reseller's own RAPP interface; it does not grant WAP root access.
Start here
- Create API logins.
- Connect and test the API login.
- Call test_connection before provisioning integration work.
Operation directory
Each operation below includes fields, responses, errors and standalone cURL/Python/PHP examples.
| Operation | Methods |
|---|---|
test_connection | GET, POST |
load-average | GET, POST |
version | GET, POST |
createacct | GET, POST |
passwd | GET, POST |
editquota | GET, POST |
changepackage | GET, POST |
changecontactemail | GET, POST |
suspendacct | GET, POST |
unsuspendacct | GET, POST |
removeacct | GET, POST |
setupreseller | GET, POST |
adminsso | GET, POST |
uappsso | GET, POST |
rappsso | GET, POST |
suspendreseller | GET, POST |
unsuspendreseller | GET, POST |
terminatereseller | GET, POST |
get_current_users_count | GET, POST |
get_current_reseller_count | GET, POST |
listsuspended | GET, POST |
accountsummary | GET, POST |
listaccts | GET, POST |
listpackages | GET, POST |
usagestatistics | GET, POST |