health

Readiness — 503 when a dependency is down

Same probes as /v1/health, but the HTTP status reflects them, so an uptime monitor can alert without parsing the body. Do not point a platform health check at this — a suspended Redis would restart-loop the API for no benefit.

Failed jobs do not 503: those are a data or upstream problem, not a reason to declare the service unfit. They appear in alerts[].

get/v1/health/ready

Request

  • Base URL: https://api.epicdirectories.com
  • URL: https://api.epicdirectories.com/v1/health/ready
  • Auth: none declared

Response

All dependencies reachable

Changes

No recorded changes to this operation across all 1 revision of this API.