All featuresA health endpoint with two assertions
API monitoringPRO
API monitoring with JSON assertions
Check that your API doesn't just respond, but responds correctly. Send any method with your headers and body, then assert on the status code and the fields in the JSON response.
POST https://api.example.com/v1/health
✓ status equals "ok"
✕ queue.depth should be less than 100 (got 412)
Real requests
GET, POST, PUT, PATCH, DELETE or HEAD, with custom headers such as an API key, and a JSON or text body.
Assertions on any field
Check nested values and list lengths: status equals ok, data.items.length greater than 0, error does not exist.
Clear failure reasons
Alerts say exactly what broke, for example: queue.depth should be less than 100 (got 412).
How to set it up
- 1Click Add monitor and choose API.
- 2Pick the method, enter the URL, and add headers and a body if the endpoint needs them.
- 3Optionally set the exact status code you expect.
- 4Add assertions on the JSON fields that matter, then save.
The details
- Methods
- GET, POST, PUT, PATCH, DELETE, HEAD
- Assertions
- equals, does not equal, contains, greater than, less than, exists, does not exist; up to 20 per monitor
- Paths
- Dot or bracket notation, e.g. data.items[0].id; .length on lists and strings
- Headers and body
- Up to 20 headers; body up to 10,000 characters
- Plan
- Pro
Questions
- Are my API keys safe?
- Headers are stored with the monitor and visible to everyone in your workspace, so use a read-only or dedicated key.
- Do HTTPS APIs get SSL checks too?
- Yes. API monitors record the certificate expiry and warn you 14 days before it lapses.
Set up api monitoring in under a minute
Available on Pro. Start free and upgrade when you need it.
Create a free account