compute

POST /v1/compute/servers/metered

Order a server paid for by the hour from the account balance.

Всички крайни точки в compute

Всички документи за разработчици

Упълномощаване

Изпратете API ключ като носител (bearer token). Тази точка за достъп не указва конкретно разрешение в спецификацията, затова дайте на ключа си най-малкото необходимо и проверете отговора, вместо да правите предположения.

Където отива идентификаторът на вашата организация

Този краен пункт приема org_id като поле в JSON тялото.

ИД на вашата организация се намира на екрана с API ключове във вашето табло за управление, до самия ключ. Това е същият ИД във всяко заявка, която правите.

Опитайте

Заменете всичко в квадратни скоби със собствени стойности, а ключовия заместващ символ – с ключ от вашето табло за управление.

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

Влязохте ли в профила си? API конзолата във вашето табло за управление попълва действителното идентификационно число на вашата организация и вашия собствен ключ и изпълнява заявката спрямо реалното API, за да можете да видите действителния отговор. Отворете този крайpoint в API конзолата

Детайли

W43-47, docs/687. Charges nothing now. The same refusals as any order apply (verification, SSH keys, zones, sizes), and three more: the account must be active, the range must be one we hold the provider account for, and the balance must cover min_funded_hours (24) at the machine's rate. A first pay-by-the-hour order grants the one-time Cloud trial credit — $10, converted into the account's own currency — before that check. Every started hour is then rated at the pinned rate, never exceeding the monthly price in a calendar month, and drawn from the balance with tax as a compute_usage order. A card on file is never charged for these hours. term_months is ignored: a metered machine has no term.

Тяло на заявката

ИмеТипЗадължителноКакво представлява
namestringДаWhat to call the machine. It is also the name at the provider, which is what lets a retried purchase find the machine it already bought instead of buying a second.
zonestringДаThe data centre, as getComputeCatalogue reported it.
specstringНеThe machine size, as the configurator reported it. ⭐ Either this or plan_code, not both — and where the provider publishes no sizes the two collapse into one, because the…
plan_codestringНеThe tier to buy, for a catalogue-aware caller. Either this or spec.
org_idUuidНеThe organisation to buy for. Required only when the caller belongs to more than one — picking "the first org in scope" would buy a server on an arbitrary tenant's balance.…
providerstringНеWhich platform to place it on. Omitted, the engine resolves the range's default — ⛔ except on a range priced per data centre (ComputeTier.zoned), where omitting it is…
imagestringНеThe operating system or one-click application the machine boots, as getComputeCatalogue reported it in ComputeProvider.images. ⛔ Required — 422 — on any range that publishes…
ssh_keysstring[]НеThe ids of the authorised keys to install at build time, from listComputeSshKeys. ⛔⛔…
blueprintstring<, bare, docker, k3s, k3s_argocd>НеW43-49 (docs/689). The software stack installed at first boot on a Zinn® Cloud machine: Docker Engine, single-machine k3s, or k3s with Argo CD. Refused on a range whose first…
term_monthsintegerНеHow many months to buy up front. Outside 1…36 is refused 422 before a single vendor write, the same bound renewComputeServer applies.
optimisationstringНеA stack optimisation profile, as the configurator reported it.
diskstringНеAn explicit disk allocation, for a provider whose supports_disk_and_bandwidth is true. Sending it to one whose is false is refused.
bandwidthstringНеAn explicit transfer allocation, for a provider whose supports_disk_and_bandwidth is true.

Отговор

ИмеТипЗадължителноКакво представлява
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>Да

Грешки, които този крайpoint може да върне

401 · 403 · 422 · 429 · 503