Skip to main content
POST
Upgrade Service
Submit an upgrade from the current service plan to a higher plan. The API creates or reuses an upgrade request and starts background processing.
A successful response means that the API accepted the request. It does not mean that the plan change is complete.

Allowed Plan Changes

An upgrade must move from a lower plan to a higher plan in this order:
  1. Basic VPS
  2. Standard VPS
  3. Professional VPS
  4. Dedicated Server
The requested plan must be above the current plan. Use the downgrade endpoint for a move to a lower plan.

Accepted Response

The normal response is HTTP 200. The plan change runs in background processing. The response does not contain an action ID, a processed date, or a completion result. Use the request ID with the list requests endpoint to check the request state.

Upgrade Processing

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

Errors

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

Upgrade accepted for processing.

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