compute

POST `/v1/compute/servers/{serverId}/root-password`

Reset a server's root password. ⛔ Reboots the machine.

Autentikasi

Kirim kunci API sebagai token bearer. Kunci tersebut harus memiliki izin sites.delete; kunci tanpa izin tersebut akan ditolak dengan status 403, bukan 404.

Endpoint ini tidak memerlukan id organisasi. Kunci Anda telah mengidentifikasi organisasi tempatnya berafiliasi, dan respons akan dibatasi untuk organisasi tersebut.

Coba

Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.

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

Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API

Detail

⭐⭐ **The other half of "I am locked out of my own server"**, and the half a console alone does not solve: the console gets you to a login prompt, and this is what you type into it when the password is the thing you lost. ⛔⛔ **The machine reboots.** The provider restarts the guest as part of applying the change, so everything running on it goes offline for a minute or two. A surface offering this must say so *before* the button, not in the result. ⛔ Requires `sites.delete`, **not** `sites.restart`: a root password is total control of the machine and everything on it, which is the same order of trust as destroying it. The server's name must be typed to confirm, and that is checked server-side — a dialog the client owns is a dialog an API caller never sees. ⛔ At least 16 characters, length only and no composition rules: this credential faces the public internet on port 22, and length is what makes it hard to guess. The value is never logged, never audited and never echoed back. `503` on a range whose provider publishes no reset (our own cloud installs an SSH key instead and mints no root password at all).

Parameter

Nama	Jenis	Wajib	Tentang apa ini
`serverId (path)`	`Uuid`	Ya	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.

Isi permintaan

Nama	Jenis	Wajib	Tentang apa ini
`password`	`string`	Ya	The new root password. At least 16 characters.
`confirm`	`string`	Ya	The server's name, typed exactly.

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 404 · 422 · 429 · 503

POST /v1/compute/servers/{serverId}/root-password