compute

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

Reinstall a server's operating system.

Alle compute Endpunkte

Authentifizierung

Senden Sie einen API-Schlüssel als Bearer-Token. Der Schlüssel muss über die Berechtigung sites.view verfügen; ein Schlüssel ohne diese wird mit 403 statt 404 abgelehnt.

Dieser Endpunkt erfordert keine Organisations-ID. Ihr Schlüssel identifiziert bereits die zugehörige Organisation, und die Antwort ist entsprechend eingeschränkt.

Ausprobieren

Ersetzen Sie alles in spitzen Klammern durch Ihre eigenen Werte und den Platzhalter für den Schlüssel durch einen Schlüssel aus Ihrem Dashboard.

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

Angemeldet? Die API-Konsole in Ihrem Dashboard trägt automatisch Ihre echte Organisations-ID sowie Ihren eigenen Schlüssel ein und führt die Anfrage gegen die Live-API aus, sodass Sie die tatsächliche Antwort sehen können. Öffnen Sie diesen Endpunkt in der API-Konsole

Details

⛔⛔ **Destructive: everything on the disk is erased and cannot be recovered.** The machine comes back on a fresh image, so the answer carries `power_state: rebooting` and a client polls from there. Three guards, and none of them is optional. The caller needs `sites.delete` rather than the key that merely spends money — `dev` may commit the organisation to a billable resource without being trusted to destroy data, so this is deliberately **not** the key `resizeComputeServer` uses. The typed confirmation is re-checked **server-side**, because a dialog a client owns is a dialog an API caller skips: `confirm` must equal the server's `name` exactly, compared case-sensitively after surrounding whitespace, and anything else is `422`. And the action is audit-logged **before** the provider is called and left in place whatever happens, because an audit row written only on success leaves no trace of an attempted wipe that errored halfway — precisely the event an investigation is looking for. ⛔ **`503` is the expected answer today, and it is honest.** No adapter currently advertises rebuild: a usable one needs the provider's own operating-system list, and an OS token we guessed would wipe a customer's machine and reinstall the wrong thing. It is a `503` rather than a `422` because it is **our** gap, and a customer told "invalid input" for a control nobody wired would retype the same thing for ever. `404` for a server that is not the caller's; `422` for an empty `operating_system` or a machine that is not `active`. Requires `sites.view` **and** `sites.delete`.

Parameter

NameTypErforderlichWas es ist
serverId (path)UuidJaThe 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.

Anfragekörper

NameTypErforderlichWas es ist
operating_systemstringJaWhich image to install, as the provider names it. ⛔ Never a string a screen or a customer composed — an OS token we guessed would wipe the machine and reinstall the wrong thing,…
confirmstringJaThe server's `name`, typed by the customer. Compared **case-sensitively** after surrounding whitespace and nothing else, so a client that forgave more would enable the button on…

Antwort

NameTypErforderlichWas es ist
idUuidJa**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.
namestringJaWhat 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_targetstringJaWhich compute range the machine belongs to.
plan_codestringJaThe tier it was bought on, or `""` when it was ordered by size alone.
providerstringJaOur provider id.
specstringJaThe machine size it currently runs.
zonestringJaThe data centre it runs in.
statusstring<pending, provisioning, active, failed, suspended, terminated>JaHow 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…
messagestringJaWhy the order failed, in a sentence the customer reads. Blank unless `failed`.
vendor_statusstringJaThe provider's own word, verbatim and unrounded. Staff-facing detail; a customer client renders `status` and never this.
power_statestring<unknown, on, off, starting, stopping, rebooting>JaWhat 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…
addressesstring[]JaPublic addresses **if the provider states them**. Empty means *not stated*, never "none" — a machine rendered as having no address reads as broken.
optimisationstringJaThe stack optimisation profile it was built with, or `""` for none.
term_monthsintegerJaThe term it was bought on, or null when the provider states none.
renews_atstringJa⛔ **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_atstringJaWhen the row was created, or `""` when not stated.
operablebooleanJaWhether 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…
imagestringJaThe provider image the machine was built from. Blank on the resold range, which installs one managed image and offers no choice.
suspendedbooleanJa⛔⛔ **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_reasonstringJaWhy, verbatim, so the customer reads the same sentence support wrote. Blank when the machine is in good standing.
capabilitiesstring[]Ja⭐⭐ **What this machine's provider can actually do** — capability tokens such as `compute:snapshots`, `compute:console`, `compute:firewall`, `compute:backups_manage` and `compute…

Fehler, die dieser Endpunkt zurückgeben kann

401 · 403 · 404 · 422 · 429 · 503