compute

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

Remove managed care — the machine becomes self-managed.

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 DELETE 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

The recurring price falls by the care amount from the next period; the paid period is honoured. Audit-logged compute.managed_care.remove. Requires sites.view and billing.payment.manage.

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.

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