Skip to main content
GET
GET /health and GET /ready

GET /health

A lightweight liveness probe. Returns 200 whenever the process is running. Does not check connectivity or contract readiness.

Response

200 OK

Error responses

None. This endpoint always returns 200 while the server process is alive.

Example

Response

GET /ready

A readiness probe. Verifies that the RPC is reachable and all six (IdentityRegistry, IdentityStaking, EventRegistry, MachineNFT, DID registry, AdminFlags) are callable. Returns 200 when all checks pass and 503 when any check fails.

Response

200 OK (all contracts ready) 503 Service Unavailable (one or more checks failed) The response body has the same shape as the 200 response, but status is "not_ready" and one or more boolean fields are false. Two failure modes produce a 503:
  • Services not initialised (server started without IDENTITY_REGISTRY_ADDRESS): every field is false, including rpc_connected and contracts.admin_flags.
  • Initialised but a check failed (RPC down, contract unreachable, etc.): only the failing fields are false. When ADMIN_FLAGS_ADDRESS is unset, contracts.admin_flags is true: AdminFlags is optional, the probe skips it, and that field never blocks readiness.

Example

Response (healthy)
Response (not ready)