# Status

> GET https://api.amodb.dev/health returns {"ok":true} when the API edge is up. It needs no key and does not count toward your rate. Repeated 500 or 504 errors across several endpoints point to an incident. Report it to support@amodb.dev with the request path, the UTC time and the HTTP status.

## Health endpoint

```bash
curl "https://api.amodb.dev/health"
```

```json
{ "ok": true }
```

Use it in your own uptime checks. It needs no key. A check every 60 seconds is enough.

## Signs of an incident

| What you see                            | Likely cause                | What to do                                                               |
| --------------------------------------- | --------------------------- | ------------------------------------------------------------------------ |
| 504 with `status_code` 24 on many paths | The backend is slow or down | Retry with a backoff; cached paths keep working                          |
| 500 with `status_code` 11 on many paths | An error on our side        | Retry after a few seconds and report it if it lasts                      |
| 429 with `status_code` 25               | Your own rate limit         | Not an incident; see [rate limits](https://amodb.dev/rate-limits/)       |
| 401 with `status_code` 7                | Key missing or wrong        | Not an incident; see [authentication](https://amodb.dev/authentication/) |

During a backend incident the edge cache keeps answering for paths it holds: details for up to 6 hours, lists for 30 minutes and images for 30 days.

## Report a problem

Write to <support@amodb.dev> with:

- the request path and query, without your key
- the time in UTC
- the HTTP status and the response body
- the values of the `X-RateLimit-*` headers, if any

Planned changes and fixes are listed in the [changelog](https://amodb.dev/changelog/).

## Related pages

- [Errors](https://amodb.dev/errors/): Every amodb error with its HTTP status, TMDB status_code and message, plus the OMDb error shape. What each one means and what your client should do next.
- [Changelog](https://amodb.dev/changelog/): Dated list of changes to the amodb API, the img.amodb.dev image host, plans and the website. New entries go on top, with what changed and what you need to do.
- [Contact](https://amodb.dev/contact/): Write to support@amodb.dev for help with keys, billing, errors or data corrections. What to include so we can answer in one reply, and who runs amodb.

Updated: 2026-10-18. Source: https://amodb.dev/status/