compute

POST /v1/compute/servers/{serverId}/managed-care

Add managed care to this machine.

All compute endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

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

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Moves the machine's recurring price up by the live managed row from the next period and the rest of the current one is charged pro rata; audit-logged compute.managed_care.add. Care is its own lane (slot=care), so it coexists with a software add-on (CloudLinux, Plesk, …). Requires sites.view and billing.payment.manage. 422 when the machine already has care or is not on a range we can look after.

Parameters

NameTypeRequiredWhat it is
serverId (path)UuidYesThe 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.

Request body

NameTypeRequiredWhat it is
currencystringNo—

Response

NameTypeRequiredWhat it is
dataManagedCareStateYesSERVERCARE-r1 — a machine's care lane, its mode and the add-on as offered.

Errors this endpoint can return

401 · 403 · 404 · 422 · 429