API monitoring that checks the response, not just the status code.
Send the real request — method, headers, body, credentials — and assert on what comes back: status code, JSON field, keyword, response time. From several European regions at once.
The request your clients send.
A health endpoint that answers 200 tells you little. Call the routes that matter, the way your clients call them.
Protected endpoints, without a false 401.
Every secret is encrypted at rest and masked everywhere it is read back.
A 200 with the wrong body is an outage.
Each option tells you which plan unlocks it.
One failing region is not an outage.
An API that fails on one network path only should not wake anyone up.
Monitors that live next to your API.
Create and change monitors from your pipeline, not only from the dashboard.
Questions about API monitoring.
All questions → HTTP monitor docs →Authentication docs →Response-time alert docs →Yes. Basic auth, Bearer token, API key, session cookie, OAuth2 client credentials and client certificates (mTLS) are available on every plan. Secrets are encrypted at rest and never returned in clear by the dashboard or the API.
Add a JSONPath assertion, for example $.status == "ok" or $.queue.size < 100. The check fails when the field is missing or the comparison is false, even if the API answers 200.
Yes. Choose the method and send a JSON, form, XML or plain-text body with your own headers. Use an endpoint without side effects, or a test account: the request runs at every check.
Every 5 minutes on Free, every 60 seconds on Pro and every 30 seconds on Max and Enterprise, from up to 2, 3 or 5 regions per monitor.
Your first monitor in under a minute.
Free plan, no card. Hosted and operated in Europe.