Validate more than a 200
Assert status codes, response headers, JSON values, and body patterns so a technically successful response cannot hide a broken service.
API monitoring
Know when an API is technically up—but functionally broken.
Assert the responses your product depends on, from status codes and headers to JSON fields and performance thresholds.
- assertion types: status, header, jsonpath, body regex
- 4
- assertion types: status, header, jsonpath, body regex
- validates the whole contract, not just the code
- 1 request
- validates the whole contract, not just the code
- status when a check passes but responds too slowly
- degraded
- status when a check passes but responds too slowly
HTTP 200 aloneMISLEADING
- Payment service silently down
- Database disconnected but the page still renders
- Cache layer missing on every request
Assertion-checkedACCURATE
- $.db.status == "healthy"
- $.cache.connected == true
- Response header + body regex checks
How it works
Contract checks for the services behind your product.
Check the data your app needs
Use JSONPath assertions to verify health fields such as database, cache, payment, or dependency status.
Catch slow success
Set a response-time threshold so a passing API that is too slow becomes a degraded, actionable signal.
Keep evidence with the incident
Failed assertions identify exactly what broke and flow through confirmation, diagnosis, notification, and incident response.
What makes it powerful
Partial failures a status code cannot express
You can assert that $.db.status == "healthy" and $.cache.connected == true in a single check, without writing any code — catching the failures that a passing status code happily hides.
Explore more features
All features →Keep moving