compute

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

Connect a Zinn® Managed machine so we can patch and watch it.

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/connect \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "access": <object> }'

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-r2 (docs/1321). Borrows one-time root access, installs the care report agent (a systemd timer that posts POST /v1/compute/care/report with a per-machine token) and enables unattended security updates. Runs as a Temporal workflow; answers 202 with the connection as it stands. Audit-logged compute.managed_care.connect with NO body (the body is a root credential). Requires sites.view and billing.payment.manage. 422 refusal.compute.careNotOnThisServer when the machine is self-managed, 422 refusal.compute.carePausedSettleAccount when care is paused for an unpaid account, 503 when the workflow service is unreachable.

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
accessobjectYes⛔⛔ Write-only. Never echoed, never logged, never audited; stored in Vault and destroyed when the connect run ends. Supply private_key or password.

Response

NameTypeRequiredWhat it is
dataManagedCareConnectionYesSERVERCARE-r2 — is the machine connected, what is pending, what was patched when. Never carries installer output or the token.

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503