Liveness + dependency health probe
Is the API process up and can it reach its dependencies. 200 when Postgres and Redis both answer, 503 with the same body shape when either does not; each dependency reports ok, the probe latency, and the error text when it failed. No key, no rate limit, not logged — made for uptime probes. It says nothing about how fresh the data is: that is GET /v1/health/coverage.
Responses
Section titled “ Responses ”Every dependency answered.
object
ok with a 200; degraded with a 503.
One entry per dependency. The keys (postgres, redis) are stable; new dependencies may be added.
object
object
How long the probe took. Absent when it threw.
The driver’s error message. Only when the probe threw.
object
How long the probe took. Absent when it threw.
The driver’s error message. Only when the probe threw.
object
How long the probe took. Absent when it threw.
The driver’s error message. Only when the probe threw.
When the probe ran.
Example
{ "status": "ok", "service": "igregulator-api", "checks": { "postgres": { "ok": true, "latency_ms": 1 }, "redis": { "ok": true, "latency_ms": 1 } }, "timestamp": "2026-10-08T00:56:22.662Z"}At least one dependency did not answer.
object
ok with a 200; degraded with a 503.
One entry per dependency. The keys (postgres, redis) are stable; new dependencies may be added.
object
object
How long the probe took. Absent when it threw.
The driver’s error message. Only when the probe threw.
object
How long the probe took. Absent when it threw.
The driver’s error message. Only when the probe threw.
object
How long the probe took. Absent when it threw.
The driver’s error message. Only when the probe threw.
When the probe ran.
Example
{ "status": "degraded", "service": "igregulator-api", "checks": { "postgres": { "ok": true, "latency_ms": 2 }, "redis": { "ok": false, "error": "Connection is closed." } }, "timestamp": "2026-10-08T00:56:22.662Z"}