Any endpoint with a URL
An API endpoint gets the same monitoring as any page — response code, response time, retries and two-check confirmation. One honest limit, stated up front: no auth headers or request-body assertions today.
What it does, plainly
Add any publicly reachable HTTPS URL — including an API route — as its own monitor. It gets a standard GET request on your schedule, with the same retry and two-check confirmation logic as every other monitor, so a real failure is still separated from a flaky blip.
- Response code and response time tracked on every check
- Keyword monitoring can confirm a specific string is present in the response body
- No custom headers, auth tokens, or POST/PUT requests — public GET endpoints, today
The details
- Standard GET request, following redirects
- Two consecutive failures required before it's treated as down
- Runs on the same schedule as your other monitors
Questions people ask
Not today — checks are unauthenticated GET requests. If this matters for your setup, tell us — it's worth a real conversation rather than a workaround.
Not as a dedicated feature. Keyword monitoring can confirm a specific string is present in the response body, which covers many common cases.
A standard GET request, following redirects.
Bring an endpoint to the call.
We'll show you exactly what gets tracked, and tell you honestly if there's a gap for your use case.