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

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

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

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点

详细信息

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.

参数

请求正文

响应

此端点可能返回的错误

401 · 403 · 404 · 422 · 429 · 503