compute
POST /v1/compute/servers/{serverId}/snapshots/{snapshotId}
Roll a server back to a snapshot.
Автентифікація
Надішліть ключ API як маркер носія (bearer token). Ключ повинен мати дозвіл sites.view; ключ без нього відхиляється з кодом 403, а не 404.
Цей кінцевий пункт не потребує ідентифікатора організації. Ваш ключ уже ідентифікує організацію, якій він належить, і відповідь обмежується її межами.
Спробувати
Замініть усе в кутових дужках власними значеннями, а заповнювач ключа — ключем із вашої панелі керування.
curl -X POST https://api.zinndigital.com/v1/compute/servers/{serverId}/snapshots/{snapshotId} \
-H "Authorization: Bearer zdk_live_…"Увійшли в систему? Консоль API у вашій панелі керування автоматично підставляє ваш реальний ідентифікатор організації та ваш власний ключ, а також виконує запит до робочого API, щоб ви могли побачити справжню відповідь. Відкрийте цю кінцеву точку в консолі API
Деталі
⛔⛔ **The most destructive operation on this API, and more so than `rebuildComputeServer`.** A rebuild gives the customer the clean machine they asked for; a restore **overwrites the live disk** with an older one. Everything written since the snapshot is gone, the current state is not itself snapshotted first, and there is no undo at the provider or here. Refused on a snapshot that is not `ready` — an image still being written restores an incomplete disk, and the provider will happily start it. Requires `sites.view` and `sites.delete`, the same key as deleting a website, because the blast radius is the same: data the customer cannot get back.
Параметри
| Назва | Тип | Обов'язкове | Що це таке |
|---|---|---|---|
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. |
snapshotId (path) | string | Так | The **provider's** id for the image, as the listing reported it — not one of ours. The engine re-checks that the snapshot was created from this machine before touching it, becau… |
Відповідь
| Назва | Тип | Обов'язкове | Що це таке |
|---|---|---|---|
id | Uuid | Так | **Ours**, and also the provisioning workflow's id and the machine's name at the provider — which is what makes the whole purchase path idempotent. |
name | string | Так | What the customer called it. ⛔ At the provider a machine's name is its row id; confusing the two is a cross-tenant defect, so this is the customer's string and nothing else. |
deploy_target | string | Так | Which compute range the machine belongs to. |
plan_code | string | Так | The tier it was bought on, or `""` when it was ordered by size alone. |
provider | string | Так | Our provider id. |
spec | string | Так | The machine size it currently runs. |
zone | string | Так | The data centre it runs in. |
status | string<pending, provisioning, active, failed, suspended, terminated> | Так | How far the order got — **ours**, and a different fact from `power_state`. `pending` is a row with nothing bought and nothing charged; `failed` is the state whose `message` is t… |
message | string | Так | Why the order failed, in a sentence the customer reads. Blank unless `failed`. |
vendor_status | string | Так | The provider's own word, verbatim and unrounded. Staff-facing detail; a customer client renders `status` and never this. |
power_state | string<unknown, on, off, starting, stopping, rebooting> | Так | What the machine is doing right now. ⛔ **Six values, not two, and the four extra ones are the point: a machine mid-transition is not "on".** `unknown` is the honest answer when… |
addresses | string[] | Так | Public addresses **if the provider states them**. Empty means *not stated*, never "none" — a machine rendered as having no address reads as broken. |
optimisation | string | Так | The stack optimisation profile it was built with, or `""` for none. |
term_months | integer | Так | The term it was bought on, or null when the provider states none. |
renews_at | string | Так | ⛔ **Always null today, and honestly so**: the provider publishes no renewal date, and one computed from the order plus the term would be our arithmetic rendered as the provider'… |
created_at | string | Так | When the row was created, or `""` when not stated. |
operable | boolean | Так | Whether the customer may act on this machine — power, resize, renew, rebuild. ⛔ Read rather than re-derived from `status`: the engine refuses every one of those on anything but… |
image | string | Так | The provider image the machine was built from. Blank on the resold range, which installs one managed image and offers no choice. |
suspended | boolean | Так | ⛔⛔ **Whether WE stopped it, which is not the same fact as `power_state`.** A stopped machine is the customer's own choice and they may start it again; a suspended one is ours an… |
suspension_reason | string | Так | Why, verbatim, so the customer reads the same sentence support wrote. Blank when the machine is in good standing. |
capabilities | string[] | Так | ⭐⭐ **What this machine's provider can actually do** — capability tokens such as `compute:snapshots`, `compute:console`, `compute:firewall`, `compute:backups_manage` and `compute… |
Помилки, які може повертати ця кінцева точка
401 · 403 · 404 · 422 · 429 · 503