compute

POST /v1/compute/care/report

A cared machine's own patch report (machine-to-engine).

All compute endpoints

All developer docs →

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

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

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/care/report \
  -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

SERVERCARE-r2 (docs/1321). Called by the care agent's timer on the customer's machine, never by a person. The Authorization: Bearer <token> header carries the per-machine token minted at connect (stored as a digest only); there is no session. 401 for an unknown token, 410 CARE_ENDED once care is removed (the agent uninstalls itself). Throttled care-report 60/min.

Request body

NameTypeRequiredWhat it is
osstringNo—
kernelstringNo—
pending_updatesintegerNo—
pending_securityintegerNo—
reboot_requiredbooleanNo—
last_patched_atintegerNoUnix seconds of the last unattended-upgrade run.
packagesstringNoThe packages that run changed, newline-separated.

Response

NameTypeRequiredWhat it is
dataobjectYes—

Errors this endpoint can return

400 · 401 · 410 · 429