API monitoring
Check multi-step API flows instead of a single endpoint.
An API monitor runs a sequence of HTTP requests and checks every response. That way you test a connected flow rather than one URL.
How it works
UptimeAlien runs your steps in order and checks each response for status code and content. At the first failing step the flow aborts and the monitor counts as down. You get a separate result per step, so you can see where the flow breaks.
When to use it
- Login, then fetch, then write as one flow instead of three separate monitors
- Checkout and signup paths where step three breaks while the first two stay green
- Everything behind authentication, where most real failures live and a plain HTTP check cannot reach
- Third-party APIs whose response changes without anyone telling you
What you get
Per-step results, response times, uptime and incidents.
Example
POST /login, then GET /health, expect status 200 per step
Frequently asked questions
What is API monitoring?
API monitoring runs a sequence of requests against your API and asserts on each response, instead of checking a single endpoint. That lets you verify a whole flow rather than one URL.
How is it different from an HTTP monitor?
An HTTP monitor checks a single request. An API monitor runs several requests in a fixed order, evaluates each one and aborts at the first failure, so you see not only that the flow failed but at which step. Every step is configured on its own, including method, headers and body.
What can I assert on?
Per step, on an expected status code and on the response containing a given string. With no status given, anything below 400 counts as fine.
Why monitor an authenticated flow?
Because most real failures happen behind the login. Put the credentials you need into fixed headers on the relevant step, a long-lived token or an API key for instance. Carrying a token from one step's response into the next request is not currently supported.