Check that your API answers correctly
A 200 with the wrong body is still an outage for your users. An HTTP(S) monitor sends the request you define and checks the answer the way your client would.
Set it up
A monitor for a JSON endpoint that must return a healthy status:
Method: POST
URL: https://api.example.com/v1/health
Headers: Authorization: Bearer ••••••
Body: {"deep": true}
Expected: 200
Response must contain: "status":"ok"How it checks.
- Method, headers and body (JSON, form data or raw text).
- Expected status codes; anything else counts as down.
- Response must contain or must not contain a text, with an option to ignore case.
- Response headers that must be present, with optional values.
- A slow-response threshold shows slow answers as Degraded instead of down.
- The alert names the monitor and what failed: the status code, the missing text or the timeout.
API monitoring: alert
The alert names the monitor and what failed: the status code, the missing text or the timeout.
Alerts go to email, Slack, Microsoft Teams, Discord, Telegram, PagerDuty or a webhook. Monitor types: HTTP(S)
See it on your own product.
Point it at your product tonight. In the morning you’ll see what happened while you slept, and which of it needed you.