Skip to main content
POST
Downgrade Service
Submit a downgrade from the current service plan to a lower plan.
A successful response means that the API accepted the request. It does not mean that the plan change is complete.

Allowed Plan Changes

A downgrade must move from a higher plan to a lower plan in this order:
  1. Dedicated Server
  2. Professional VPS
  3. Standard VPS
  4. Basic VPS
The endpoint rejects a request for the current plan. It also rejects a move to a higher plan. Use the Upgrade Service endpoint for a move to a higher plan.

Accepted Response

The endpoint returns HTTP 200 after it queues the work. The response does not contain an internal request UUID, an action ID, or a completion time.

Downgrade Processing

A reboot of the client’s service is required for finalizing the downgrade. Therefore, once a downgrade request is submitted the client will receive an email containing the next required steps to complete the downgrade process. The downgrade to the client’s service is not applied until they perform the required steps.

Errors

All error responses have success: false and an error object.

Authorizations

Authorization
string
header
required

Send the API key in the Authorization bearer header. Production keys begin with sk_live_.

Path Parameters

service_number
integer<int64>
required

Public service number parsed as a base-10 integer.

Body

application/json
new_plan
string
required

Target plan slug or label, accepted case-insensitively. Valid slugs are basic-vps, standard-vps, professional-vps, and dedicated-server.

Response

Downgrade accepted for processing.

success
boolean
required
data
object
required
message
string
pagination
object
Last modified on August 2, 2026