Health check
The health check tells monitors whether the API is up. It needs no token and deliberately carries no version prefix.
Every endpoint below shows its parameters and response fields in the middle and a request sample with an example response on the right.
Liveness check of the Public API
/healthNo authenticationLightweight liveness/health probe for monitoring and uptime checks (e.g. a load balancer or status page). Requires NO authentication (no Bearer token) and reads no tenant data and no database — it only confirms that the API process is up and answering, and reports which service/environment/version responded.
Field overview from the specification
Response fields:
status(string): health status; alwaysokwhen the service answers.service(string): name of the service that responded.environment(string): environment the service runs in (e.g.dev,prod).version(string): version of the running service.timestamp(string): time the response was produced (UTC ISO-8601).
Possible outcomes:
- 200: the service is running (body as above). This endpoint itself only ever returns
200when reached. - no response / 502 / 503 / 504: returned by the gateway/infrastructure, NOT by this endpoint, when the service is down, still starting, or unreachable — a missing or non-2xx answer is exactly the "unhealthy" signal a liveness probe checks for.
Response
statusstringrequiredHealth status of the service;
okwhen it is running.Example:okservicestringrequiredName of the service that answered.
environmentstringrequiredEnvironment the service runs in (e.g.
dev,prod).versionstringrequiredVersion of the running service.
timestampstringrequiredTime the response was produced (UTC ISO-8601).
Status codes
- 200Service is running.