system

GET /readyz

Readiness probe — are this instance's workers warm and can it reach its database.

All system endpoints

All developer docs →

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 GET https://api.zinndigital.com/readyz

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

Unauthenticated. 200 when every worker of this instance has finished its boot work and the instance can run a query; 503 otherwise (reason says which), so the orchestrator sends no request to an instance that is still starting or could only fail. Liveness stays on /healthz.

Response

NameTypeRequiredWhat it is
statusstring<ready, not_ready>Yes—
reasonstring<database, warming>No—
warmintegerNoWith reason=warming, how many of this instance's workers are warm.
workersintegerNoWith reason=warming, how many workers must be warm before it is ready.
versionstringNo—

Errors this endpoint can return

503