API monitoring
Run your requests and flows on a schedule, assert on every result, and get alerted the moment something fails or slows down. Turn the same checks into a public status page your users can trust.
A monitor runs an actual request or flow on an interval you choose, the same calls your tests use, not a shallow ping. That means a monitor catches a broken login or a malformed payload, not just a server that happens to answer on port 443.
Because monitors reuse your collections, there is nothing to re-create, and the check stays honest as the API evolves.
A 200 is not the same as correct. Assert on status, response time, body shape, and specific values, so a monitor goes red when the response is wrong, not only when the request fails outright.
Every run records whether it passed and how long it took, so you get an uptime percentage and a latency history per monitor. Slow degradation shows up as a rising line well before it becomes an outage.
When a monitor fails or breaches a latency limit, it alerts by email or webhook, so the right people know in minutes. Route failures into the channels your team already watches.
Alerts fire on the assertion result, so you are paged for a genuinely wrong response, not a transient blip you did not care about.
Publish a status page backed by your monitors so customers see current status and history without emailing support. Let them subscribe to be notified when something breaks and when it is fixed.
Point a monitor at a request or flow from your collection and choose how often it runs.
Add assertions on status, latency, and body so a wrong response counts as a failure.
Choose who gets paged by email or webhook when a monitor fails or slows down.
Turn the monitors into a public status page your customers can watch and subscribe to.
A monitor runs your real request or flow and asserts on the result, so it catches a broken login or a malformed payload, not just whether the server answers.
A failed assertion or a breached latency limit. Alerts go out by email or webhook, so you are notified about genuinely wrong responses within minutes.
Yes. A monitor points at a request or flow from your collection, so there is nothing to re-create and the check stays accurate as the API changes.
Publish a status page backed by your monitors. It shows current status and history, and visitors can subscribe to be notified about incidents and recovery.
The desktop app is free and open source. Add the cloud when you want hosted mocks, monitoring, and a shared broker.