API endpoint monitoring

What it does

An API monitor is a monitor whose health is decided by the response, not just by the server answering. On your plan's schedule, Monitrova sends the request you configured — method, headers and body — and evaluates your pass conditions. If any condition fails for long enough, it opens an incident and emails you, exactly like a website going down.

Add one from Add site: choose API endpoint as the monitor type, enter the URL, pick the method, add any headers (e.g. Authorization: Bearer …) and a body, then set your conditions. You can try the same request first with the free API Endpoint Checker.

How to add an API monitor

1. Go to Add site and choose "API endpoint" as the monitor type.
2. Enter the endpoint URL and select the HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS).
3. Add request headers (one per line) and, for write methods, a request body.
4. Set your pass conditions: expected status code, max response time, body-contains text, and a JSON field path (optionally equal to a value). The expected status is the "Expected HTTP status" field in monitoring settings.
5. Save. The monitor runs on your plan's interval; use Recheck to run it on demand.

Monitor status

Status	What it means
Up	The most recent check met every pass condition you set.
Down	The endpoint was unreachable, or a pass condition failed — the failed condition is recorded with the check.
Unknown	No check has run yet, or the monitor is paused.

Pass conditions you can set

Condition	What it means
Expected status code	The response must return this exact HTTP status (e.g. 200, 201, 204).
Max response time	The response must arrive within this many milliseconds.
Body contains	The response body must contain this exact substring.
JSON field path	A dot-path (e.g. data.status) that must exist in the JSON response — and, if you set a value, must equal it.

Good to know

• An API monitor counts as one site against your plan's site limit.
• Health is decided by your conditions: with none set, any non-error (2xx/3xx) response is healthy.
• Incidents, email/webhook alerts and uptime history work exactly like website monitors.
• Request headers and body are stored so the same request can be replayed on schedule — only add credentials you're comfortable storing.

Related guides

• Add & configure a monitor
• Incidents
• API Endpoint Checker