compute

POST `/v1/compute/servers/{serverId}/backups/tier`

Move the machine between the standard and extended backup tiers.

身份验证

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

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

免费试用

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

curl -X POST https://api.zinndigital.com/v1/compute/servers/{serverId}/backups/tier \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "tier": <string<standard, pro>> }'

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

详细信息

⛔⛔ **Chargeable one way and lossy the other.** Upgrading starts a recurring charge for as long as it runs. Downgrading returns the machine to the standard retention, and what happens to the snapshots already taken is the provider's decision and is not documented — so a confirmation should say the tier changes and must **not** promise a date for the older restore points. The response is the tier **re-read from the provider**, never an echo of the request. Requires `billing.payment.manage`.

参数

名称	类型	必填	内容简介
`serverId (path)`	`Uuid`	是	The server's id, as `listComputeServers` reports it. Ours (UUIDv7), minted when the order row was written — never the provider's own identifier for the machine.

请求正文

名称	类型	必填	内容简介
`tier`	`string<standard, pro>`	是	⛔ Ours, not the provider's. `standard` maps to their `normal` and `pro` to their `upgraded`; the mapping lives in the engine so a client never learns a vendor word.

响应

名称	类型	必填	内容简介
`data`	`ComputeBackupTier`	是	A machine's backup tier and the price of moving it. ⛔ `tier` is the provider's own word, verbatim (`normal` / `upgraded`), because rounding it to a boolean loses the difference…

此端点可能返回的错误

401 · 403 · 404 · 422 · 429 · 503

POST /v1/compute/servers/{serverId}/backups/tier