terminatereseller — WAP API
Terminate a reseller and its accounts through the WAP root administrator API, with request fields, response details, errors and cURL/Python/PHP examples.
/api/v1/terminatereseller/Also accepts GETPermanently removes the reseller and its account tree through the reseller-wide removal command. This is broader than removing one hosting account and has no dry-run or additional confirmation parameter. Review all affected customers and retain tested backups before calling it. The wrapper does not check the CLI exit status; verify the actual removals and server logs even when the API returns success.
Request
| Property | Value |
|---|---|
| Methods | GET, POST |
| Versioned path | /api/v1/terminatereseller/ |
| Default path | /api/terminatereseller/ |
| Authentication | WAP root administrator API credentials. |
| Header | Required value |
|---|---|
X-API-USER | Your WAP API username. |
X-API-PASSWORD | Its API password. |
Parameters
| Field | Required | Type and behavior |
|---|---|---|
user | Yes | String. Existing reseller username; required state is described above. |
POST reads the JSON/form body; GET reads query parameters. The examples use form-encoded POST. Although GET is supported, use POST for account changes and login-link generation so action fields are not placed in URLs. Authentication remains in the two headers. Undeclared fields are not additional API options.
Replace server.example.com, 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.
Permanent removal
This request deletes hosting resources. Verify the target and affected account tree and retain tested backups before running an example.
Success response
HTTP 200. Illustrative values; account records and server values vary. Stored account examples show only selected fields.
{
"data": "Reseller account terminated exampleuser",
"info": "Hosting reseller account terminated successfully",
"status": 200
}| Field | Type | Meaning |
|---|---|---|
status | integer | 200 on the documented success branch. |
info | string | Operation description. |
data | string | Success message. |
Verify the resulting account state and logs independently: the command wrapper does not validate the CLI exit code.
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. |
| Invalid/missing operation fields or invalid target state | 400 | Field errors in error; JSON status: 400. |
| Backend reports failure | 400 | Operation error in error; JSON status: 500. |
| Unsupported method | 405 after authentication | Method-not-allowed response. |
Validation failure description: Unable to terminate reseller hosting account. The data is invalid.
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.