get_current_users_count — Reseller API
Count hosting accounts through the Reseller API, with request fields, response details, errors and cURL/Python/PHP examples.
/api/v1/get_current_users_count/Also accepts GETCounts entries in the authenticated reseller configuration accounts list. It does not validate each entry against a hosting-user file, and a self-owned reseller can be included if present in that list. Missing, unreadable or incorrectly shaped registry data produces zero. This is not a global server count.
Request
| Property | Value |
|---|---|
| Methods | GET, POST |
| Versioned path | /api/v1/get_current_users_count/ |
| Default path | /api/get_current_users_count/ |
| 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": {
"users": 12
},
"info": "Total number of Eenos hosting accounts",
"status": 200
}| Field | Type | Meaning |
|---|---|---|
status | integer | 200 on the documented success branch. |
info | string | Operation description. |
data | object | Operation data described below. |
data.users | integer | Integer count of list entries. |
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. |
| Caught backend exception | 400 | Exception text in error; JSON status: 500. |
| 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.