Health
2 routes. Paths are relative to https://api.intersink.com/v1.
Health check
GET/health
Public: no sign-in needed.
Liveness: the process is up. Never touches dependencies.
Response
200. The payload in data is not described in the spec yet.
Readiness check (Directus reachability)
GET/health/ready
Public: no sign-in needed.
Readiness: can this instance serve traffic (Directus reachable)? 200 when ready, 503 when not, with the same envelope either way so probes and humans can read it. Reports states only; never URLs or error text. Redis makes the instance unready only when REDIS_REQUIRED is on (multi-instance deploys); otherwise "off" means cross-instance state (realtime, relay mailboxes, rate limits) is per instance. Kosh (our own Postgres pool) is checked too: "off" without KOSH_DATABASE_URL, else "up" or "down". It makes the instance unready only while some module reads from it (pg mode); in directus and shadow mode Directus answers every request, so a Kosh outage only pauses shadow comparisons.
Response
200. The payload in data is not described in the spec yet.