UptimePad monitors your API endpoints the same way it monitors websites: it sends a real request on a schedule, then checks the status code, response time, response body, and headers against the rules you set. When an endpoint returns the wrong code, slows past your SLO, or stops matching its expected response, you get alerted on the channel you choose.
| Tool | Up/down + status code | Response time | Body & header assertions | Fastest check | Monthly price |
|---|---|---|---|---|---|
| UptimePad Free No card, commercial use allowed | ✓ | ✓ | - | 5 min | $0 |
| UptimePad Starter | ✓ | ✓ | - | 1 min | $12 |
| UptimePad Pro Adds response assertions + SLO | ✓ | ✓ | ✓ | 1 min | $39 |
| UptimePad Scale | ✓ | ✓ | ✓ | 30 sec | $99 |
The trap with API monitoring is treating a 200 OK as success. An endpoint can return 200 with an empty array, a stale cache, an error wrapped in a success envelope, or a payload missing the field your clients depend on. A plain uptime ping calls that healthy. Real API monitoring checks the contract:
On the Pro plan and above, each API monitor can carry response assertions and a response-time SLO. Assert that the body contains a keyword or matches a pattern, require a specific header, and set the latency budget the endpoint must stay under. When a check fails an assertion or blows the SLO, UptimePad opens an incident and alerts your channel, the same way it would for a hard outage. Free and Starter monitor availability, status code, and response time on every check; assertions and the SLO are the Pro upgrade.
Point a monitor at any HTTP or HTTPS endpoint: a REST API, a health route, a webhook receiver, a GraphQL gateway over HTTP. Configure the request method and the headers the endpoint needs, including an authorization token for protected routes, and UptimePad runs the check from its own probe regions. Because the API endpoint also rides on UptimePad’s SSL and DNS monitoring, you catch an expiring certificate or a DNS change on the API host on the same timeline.
UptimePad monitors your APIs, and it ships a public REST API of its own so you can manage monitors, fetch results, and wire monitoring into your own tooling. The read API is on the free plan; full read and write access is on Starter and above. See the docs for endpoints, or the pricing page for the per-plan limits.
Yes. Point a monitor at any HTTP or HTTPS endpoint and UptimePad sends a real request on your schedule, checking the status code and response time on every plan, plus response-body and header assertions on Pro and above.
Configure the request headers the endpoint requires, including an authorization token, on the monitor. UptimePad sends those headers with each check so protected endpoints can be monitored without exposing the route publicly.
A rule the response must satisfy beyond returning 200: the body contains a keyword or matches a pattern, a specific header is present, and the response stays under a response-time SLO. Assertions are available on the Pro plan and above. A failed assertion opens an incident and alerts you.
Yes, on Pro and above. Set the latency budget the endpoint must stay under, and UptimePad alerts you when a check exceeds it, even if the endpoint still returned a 200.
As fast as every 30 seconds on Scale, every minute on Starter and Pro, and every 5 minutes on Free. Multi-region monitors can also require a 2-of-N regional consensus before an alert fires, which removes single-region false positives.
No. API endpoints are monitored as standard HTTP monitors and count against your plan monitor limit. Availability and response-time monitoring are on the free plan; response assertions and SLOs are part of Pro at $39 per month.
Add an endpoint, set the expected response, and get alerted when the contract breaks. Free plan covers availability and response time with no credit card.
Start monitoring free →