meta

Liveness: is the process up and can it reach the database

A cheap check for load balancers: always 200. status is ok, or degraded when the database does not answer. database is "up", "busy" (every pooled connection is in use right now: the service is loaded, not broken, and status stays ok) or "down". commit is the git commit this image was built from, "unknown" outside a deploy. runs_in_flight counts research runs queued or running across the service (null when the database did not answer): a restart waits for 0, because Railway's in-place restart kills the process about 10 seconds after SIGTERM. It waits at most about 2 seconds for a connection and never calls a provider.

get/health

Request

  • Base URL: https://api.hookdetector.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.hookdetector.com/health
  • Auth: none declared

Response

Successful Response

versionstring required
commitstring nullable

the git commit this image was built from; "unknown" outside a deploy

started_atstring nullable

when this process started (ISO 8601); a new value means a restart

runs_in_flightinteger nullable

research runs queued or running across the service right now; null when the database did not answer. An operator restarts only at 0

Example response

{
  "commit": "5d3194d0c1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6",
  "database": "up",
  "runs_in_flight": 0,
  "started_at": "2026-09-23T16:11:02.123456+00:00",
  "status": "ok",
  "version": "2.4.0"
}

Changes

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