OVOK DOCS
Get startedOvokSignalsSDKsGuidesAPI referenceDeveloper resources
Healthcheck

Check Redis health

  • Sandbox: available
  • Staging: available
  • Production: unknown
GET
/redis

Checks whether the backend can reach Redis.

Auth: none. The route needs no bearer token.

Behaviour

  • Sends a PING to Redis. ok is true only when Redis answers PONG, and false on any error.
  • The status is 200 in both cases.
  • Unlike GET /healthcheck, this probe has no time limit of its own.

Example

curl -X GET 'https://api.sandbox.ovok.com/healthcheck/redis'
{ "ok": true }

Response Body

Redis health status.

Example Request
curl -X GET 'https://api.sandbox.ovok.com/redis'
Example Response
Empty

Get application readiness GET

Returns the same body as the liveness healthcheck, but with the verdict in the HTTP status. Use it for monitors and alerts that page on status code. **Auth:** none. The route needs no bearer token. ## Behaviour - Runs the same bounded Redis and FHIR store probes as `GET /healthcheck`. - Answers `200` when `ok` is `true` and `503` when it is `false`. The `503` body is the same healthcheck result, so `dependencies` still names the failing dependency. - Do not use this route for container liveness probes: a failing dependency would make the orchestrator restart a backend that is merely degraded. ## Example ```bash curl -X GET 'https://api.sandbox.ovok.com/healthcheck/ready' ```

Check Redis health GET

Checks whether the backend can reach Redis. **Auth:** none. The route needs no bearer token. ## Behaviour - Sends a `PING` to Redis. `ok` is `true` only when Redis answers `PONG`, and `false` on any error. - The status is `200` in both cases. - Unlike `GET /healthcheck`, this probe has no time limit of its own. ## Example ```bash curl -X GET 'https://api.sandbox.ovok.com/healthcheck/redis' ``` ```json { "ok": true } ```