Ready
GET/ready
Readiness check for dependencies required to serve API traffic.
Probes the database, object storage, and serverless function gateway concurrently and reports each as ok or
degraded with the failing exception's type name (never its message, since this endpoint
is reachable without authentication). The overall status is ok only when every check
passes; otherwise the response body still reports degraded per-check detail, but the HTTP
status is set to 503 so an orchestrator can act on the status code alone without parsing the
body.
Responses
- 200
- 503
Successful Response
One or more upstream dependencies are unavailable