compute
GET /v1/compute/servers/{serverId}/managed-care
Who looks after this machine — self-managed or Zinn® Managed — and the care add-on's live price.
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 GET https://api.zinndigital.com/v1/compute/servers/{serverId}/managed-care \
-H "Authorization: Bearer zdk_live_…"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
SERVERCARE-r1 (owner 2026-11-11). management_mode is self_managed (no care add-on: server work is the customer's, and a request for it is answered with this add-on), zinn_managed (we patch, monitor and are on call), or zinn_managed_paused (the add-on is held but the account is not in good standing, §2.46 — care pauses and resumes by itself on payment). offer is the LIVE managed catalogue row in currency. Requires sites.view.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
serverId (path) | Uuid | Yes | 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. |
currency (query) | string | No | ISO currency to price the offer in. Defaults to USD. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | ManagedCareState | Yes | SERVERCARE-r1 — a machine's care lane, its mode and the add-on as offered. |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429