Docs / API and agents

Health, status and scheduled jobs

Liveness, readiness and public status endpoints, and the jobs the services run on a clock.

Endpoints (all public)#

Method and pathMeaning
GET /healthliveness: { status: "ok" }, used by the container healthcheck
GET /health/readyreadiness: runs SELECT 1; 503 database_unavailable if the database does not answer
GET /statuscomponent checks for the status page (no-store)
GET /health/readinessfor monitors: 200 { ok, checkedAt, monitoringCurrent } when the database answers and the recorded monitoring is fresh and healthy; otherwise 503. It never reveals service details

Jobs#

There are no cron routes. The schedule and the work live in apps/services/src/jobs (UTC, one run at a time per job). The full list of crons and queues, with schedules, is in Scheduled jobs and queues; the one this page cares about is monitoring (every 5 minutes, records the snapshot that GET /health/readiness and /platform/health read).

  • Staff operations API