Skip to Content
Browse documentation

changepackage — Reseller API

Change the hosting package through the Reseller API, with request fields, response details, errors and cURL/Python/PHP examples.

POST/api/v1/changepackage/Also accepts GET

Applies the selected existing hosting package to the account and updates its package-controlled limits, including disk quota and inherited email limits. Current package-change code preserves the existing shell and dedicated-IP choices rather than provisioning a new IP. Review the target package and verify the resulting limits after the change.

Request

The selected account must be in the authenticated reseller accounts list and have a hosting-user file. Other resellers’ accounts are rejected with HTTP 400 and JSON status 400; this is an ownership check, not an authentication failure.

This handler rejects changes to a suspended target account with HTTP 400 and JSON status 400.

The selected package must be owned by the authenticated reseller; a globally existing package is not sufficient. Ownership rejection returns HTTP 400 and JSON status 400.

PropertyValue
MethodsGET, POST
Versioned path/api/v1/changepackage/
Default path/api/changepackage/
AuthenticationReseller API credentials.
HeaderRequired value
X-RESELLERThe reseller account owning these API credentials.
X-API-USERYour Reseller API username.
X-API-PASSWORDIts API password.

Parameters

FieldRequiredType and behavior
userYesString. Existing hosting username; required account state is described above.
packageYesString. Existing hosting package name, without the .yaml suffix.

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, 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": "User hosting package changed for exampleuser",
  "info": "Hosting account package changed successfully",
  "status": 200
}
FieldTypeMeaning
statusinteger200 on the documented success branch.
infostringOperation description.
datastringSuccess message.

Errors and demo mode

ConditionActual HTTP statusResponse behavior
Missing credentials with no other authenticated identity403detail: Authentication credentials were not provided.
Rejected password or source IP403detail: Invalid API credentials
Demo server400error: Demo server; info: Api Operations not available in demo server; JSON status: 403.
Invalid/missing operation fields or invalid target state400Field errors in error; JSON status: 400.
Backend reports failure400Operation error in error; JSON status: 500.
Unsupported method405 after authenticationMethod-not-allowed response.

Validation failure description: Unable to change hosting account package. 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.

See Reseller API authentication and connection troubleshooting.