POST /v1/compute/servers/{serverId}/resize

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/compute/servers/{serverId}/resize \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Performs the upgrade and returns the server's new state. ⛔ This charges immediately at every provider we support, so it is only ever reached from a quote the customer has read (quoteComputeServerResize). The engine attaches an idempotency key derived from the server and the target size, so a retry cannot buy the resize twice. ⛔⛔ A size whose disk is smaller than what the machine is already using is refused with a 422, and that is a data-loss gate rather than a tidiness check. The provider's endpoint is an upgrade endpoint and usually refuses a shrink, but "usually" is not a promise to make about a customer's files. Before a shrink the engine reads the machine's live disk usage and requires the target to be strictly larger. It fails closed: if the provider does not answer, or answers -1 ("did not say"), the resize is refused rather than attempted — -1 < anything would otherwise read as "plenty of room". Growing is never gated, never pays for the extra read, and never fails because usage statistics were unavailable. RAM is not gated: running with less memory loses nothing on disk and is the customer's call. 404 for a server that is not the caller's; 422 for a size the provider does not offer, a machine that is not active — an order still running would have two writers, and a failed or released one has nothing to write to — or a shrink below the disk in use. Requires sites.view and billing.payment.manage — ⛔ not sites.create, which is what this was until #1682.

Parameters

Request body

Response

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503