compute

POST /v1/compute/servers/metered

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

Tous les points de terminaison compute

Toute la documentation pour développeurs

Authentification

Envoyez une clé d'API en tant que jeton du porteur (bearer token). Cet endpoint n'indique pas de permission spécifique dans la spécification, attribuez donc à votre clé le minimum requis et vérifiez la réponse plutôt que de faire des suppositions.

Où insérer l'ID de votre organisation

Cet endpoint prend org_id comme champ dans le corps JSON.

L'identifiant de votre organisation se trouve sur l'écran des clés API de votre tableau de bord, à côté de la clé elle-même. Il s'agit du même identifiant pour chaque appel que vous effectuez.

Essayer

Remplacez tout ce qui se trouve entre crochets par vos propres valeurs, et le espace réservé à la clé par une clé de votre tableau de bord.

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> }'

Connecté ? La console d'API de votre tableau de bord saisit votre véritable ID d'organisation ainsi que votre propre clé, et exécute la requête sur l'API de production afin que vous puissiez voir la réponse réelle. Ouvrir ce point de terminaison dans la console API

Détails

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.

Corps de la requête

NomTypeObligatoireQu'est-ce que c'est
namestringOuiWhat 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.
zonestringOuiThe data centre, as getComputeCatalogue reported it.
specstringNonThe 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_codestringNonThe tier to buy, for a catalogue-aware caller. Either this or spec.
org_idUuidNonThe 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.…
providerstringNonWhich 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…
imagestringNonThe 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[]NonThe ids of the authorised keys to install at build time, from listComputeSshKeys. ⛔⛔…
term_monthsintegerNonHow many months to buy up front. Outside 1…36 is refused 422 before a single vendor write, the same bound renewComputeServer applies.
optimisationstringNonA stack optimisation profile, as the configurator reported it.
diskstringNonAn explicit disk allocation, for a provider whose supports_disk_and_bandwidth is true. Sending it to one whose is false is refused.
bandwidthstringNonAn explicit transfer allocation, for a provider whose supports_disk_and_bandwidth is true.

Réponse

NomTypeObligatoireQu'est-ce que c'est
idUuidOuiOurs, and also the provisioning workflow's id and the machine's name at the provider — which is what makes the whole purchase path idempotent.
namestringOuiWhat 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_targetstringOuiWhich compute range the machine belongs to.
plan_codestringOuiThe tier it was bought on, or "" when it was ordered by size alone.
providerstringOuiOur provider id.
specstringOuiThe machine size it currently runs.
zonestringOuiThe data centre it runs in.
statusstring<pending, provisioning, active, failed, suspended, terminated, resizing, terminating>OuiHow 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…
messagestringOuiWhy the order failed, in a sentence the customer reads. Blank unless failed.
vendor_statusstringOuiThe 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>OuiWhat 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[]OuiPublic addresses if the provider states them. Empty means not stated, never "none" — a machine rendered as having no address reads as broken.
optimisationstringOuiThe stack optimisation profile it was built with, or "" for none.
term_monthsintegerOuiThe term it was bought on, or null when the provider states none.
renews_atstringOuiAlways 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_atstringOuiWhen the row was created, or "" when not stated.
operablebooleanOuiWhether 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…
imagestringOuiThe provider image the machine was built from. Blank on the resold range, which installs one managed image and offers no choice.
suspendedbooleanOui⛔⛔ 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_reasonstringOuiWhy, verbatim, so the customer reads the same sentence support wrote. Blank when the machine is in good standing.
capabilitiesstring[]Oui⭐⭐ What this machine's provider can actually do — capability tokens such as compute:snapshots, compute:console, compute:firewall, compute:backups_manage and…
billingComputeServerBillingOuiHow 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…

Erreurs que cet point de terminaison peut renvoyer

401 · 403 · 422 · 429 · 503