---
title: "Check HTTP Server and Database Status"
method: GET
path: "/health/ready"
tags: ["metadata"]
---

# Check HTTP Server and Database Status

`GET /health/ready`

This endpoint returns a HTTP 200 status code when Ory Oathkeeper is up running and the environment dependencies (e.g.
the database) are responsive as well.

If the service supports TLS Edge Termination, this endpoint does not require the
`X-Forwarded-Proto` header to be set.

Be aware that if you are running multiple nodes of Ory Oathkeeper, the health status will never
refer to the cluster state, only to a single instance.

## Response `200`

Ory Oathkeeper is ready to accept requests.

- object
  - `status` string, required — Always "ok".

## Other responses

- `503` — Ory Kratos is not yet ready to accept requests.
- `default` — Unexpected error

## Changes

- **2022-02-08** `4a4308530ea1` — 5 info
  - api operation id `isInstanceReady` removed and replaced with `isReady`
  - api tag `metadata` added
  - api tag `api` removed
  - added the media type `application/json` for the response with the status `200`
  - …1 more
- **2021-04-26** `26e7abf193b0` — 2 breaking, 3 info
  - removed the media type `application/json` for the response with the status `200`
  - removed the media type `application/json` for the response with the status `503`
  - api operation id `isReady` removed and replaced with `isInstanceReady`
  - api tag `api` added
  - …1 more

[Change history](https://skmtc.dev/ory/apis/ory-oathkeeper-api/changes/health/ready/get.md)

---

[API](https://skmtc.dev/ory/apis/ory-oathkeeper-api.md) · [All operations](https://skmtc.dev/ory/apis/ory-oathkeeper-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ory/ory-oathkeeper-api/revisions/3a8f56666af1/schema)