Баталгаажуулалт

API түлхүүрийг bearer token хэлбэрээр илгөэнэ үү. Түлхүүр нь sites.restart эрхтэй байх ёстой бөгөөд үүнгүйгээр 404 биш, харин 403 алдаа буцааж татгалзах болно.

Энэ төгсгөл цэг нь ямар ч байгууллагын ID шаардахгүй. Таны түлхүүр аль хэдийн харьяалагдах байгууллагыг тодорхойлж байгаа бөгөөд хариу нь тухайн байгууллагын хүрээнд хязгаарлагдана.

Туршиж үзэх

Өнцөг хаалтанд байгаа бүх зүйлийг өөрийн утгаар солиж, түлхүүр санамж байрлуулагчийг хяналтын самбарынхаа түлхүүрээр сольж оруулна уу.

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

Та нэвтэрсэн байна уу? Таны хяналтын самбар дахь API консол нь таны бодит байгууллагын ID болон өөрийн түлхүүрийг автоматаар бөглөж, шууд ажиллаж буй API рүү хүсэлт илгээх тул та бодит хариуг харах боломжтой болно. Энэ төгсгөлийн цэгийг API консол дээр нээх

Дэлгэрэнгүй

Set the machine's display name. The provider is changed first and our own record only if it agreed, so a customer is never shown a name their provider has never heard of. Names are limited to 37 characters because that is what the provider enforces. A name the provider refuses - too long, or already used on the account - returns 422 and changes nothing. Requires sites.restart.

Параметрүүд

НэрТөрөлЗаавал шаардлагатайЭнэ юу вэ
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.

Хүсэлтийн бие

НэрТөрөлЗаавал шаардлагатайЭнэ юу вэ
namestringТиймThe machine's new display name. 37 characters is the provider's own limit, mirrored here so the refusal comes from this form rather than from the supplier.

Хариу үйлдэл

НэрТөрөлЗаавал шаардлагатайЭнэ юу вэ
idUuidТийм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.
namestringТийм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_targetstringТиймWhich compute range the machine belongs to.
plan_codestringТиймThe tier it was bought on, or "" when it was ordered by size alone.
providerstringТиймOur provider id.
specstringТиймThe machine size it currently runs.
zonestringТиймThe data centre it runs in.
statusstring<pending, provisioning, active, failed, suspended, terminated, resizing, terminating>Тийм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 the…
messagestringТиймWhy the order failed, in a sentence the customer reads. Blank unless failed.
vendor_statusstringТиймThe 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>Тийм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…
addressesstring[]ТиймPublic addresses if the provider states them. Empty means not stated, never "none" — a machine rendered as having no address reads as broken.
optimisationstringТиймThe stack optimisation profile it was built with, or "" for none.
term_monthsintegerТиймThe term it was bought on, or null when the provider states none.
renews_atstringТийм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's…
created_atstringТиймWhen the row was created, or "" when not stated.
operablebooleanТийм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…
imagestringТиймThe provider image the machine was built from. Blank on the resold range, which installs one managed image and offers no choice.
suspendedbooleanТийм⛔⛔ 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 and…
suspension_reasonstringТиймWhy, verbatim, so the customer reads the same sentence support wrote. Blank when the machine is in good standing.
capabilitiesstring[]Тийм⭐⭐ What this machine's provider can actually do — capability tokens such as compute:snapshots, compute:console, compute:firewall, compute:backups_manage and…
billingComputeServerBillingТиймHow a machine is paid for (W43-47, docs/687). term machines are charged ahead by a per-machine subscription. metered machines are charged per started hour from the account…
login_userstringТиймThe account to sign in as (W43-49, docs/689). admin — key-only, passwordless sudo, root login refused — on a Zinn® Cloud machine built under the access model; root on one…
blueprintstring<, docker, k3s, k3s_argocd>ТиймThe software stack installed at first boot. Blank for none.
cluster_idstringТиймThe cluster this machine is a node of, or blank.
cluster_rolestring<, server, agent>Тийм

Энэ төгсгөл цэгээс буцааж болох алдаанууд

401 · 403 · 404 · 422 · 429 · 503