API uptime monitoring & API health checks
Monitor REST API uptime, response status, and multi-step flows. Catch failed endpoints and slow responses with alerts by email, Telegram, or webhook — before integrations and users stall.
What API monitoring covers
Run scheduled requests against your public or internal APIs (reachable from SitePuls). Verify HTTP status codes, response times, and — for REST monitors — JSON bodies using assertions. Multi-step flows let you log in, reuse tokens, and chain calls like real clients do.
Multi-step flows and validation
Extract values from a response (for example access tokens) and pass them to the next step. Assert on status codes, JSON paths, or latency budgets. If any step fails, the run fails and you’re notified — matching how SitePuls actually executes checks today.
Failures and downtime you can detect
Broken auth, unexpected 4xx/5xx responses, regressions after deploys, and slow endpoints that breach your thresholds. Track whether an API is “up” in a meaningful way, not only that TCP connects.
Who uses API monitors
SaaS teams protecting public integrations, agencies maintaining client backends, and internal tool owners who need a simple health signal without running a full observability suite.
Public and internal APIs
Public HTTPS endpoints are straightforward. Internal APIs must be reachable from SitePuls over the network paths you expose — there is no in-network agent; plan VPN or edge access accordingly.
Alerting workflow
Failed runs open incidents and notify contacts through the same channels as other monitors: email, Telegram, webhook. Review duration and history in the dashboard when you triage.
Pair with heartbeat monitoring
When a backend depends on batch jobs or queues, combine API checks with heartbeat monitors so you know both the HTTP surface and scheduled work are alive.
Getting started
Create a REST API monitor, define steps, headers, and assertions, then pick an interval and contacts. SitePuls executes the flow on schedule from our infrastructure and surfaces failures immediately.
Frequently asked questions
What is API monitoring?
API monitoring regularly checks your REST API endpoints (or multi-step flows) from our infrastructure. If a check fails or response time degrades, you get an alert. It helps you keep APIs reliable and fix issues before users or dependent systems are affected.
Can I monitor multi-step API flows?
Yes. SitePuls supports multi-step API monitoring. You can extract values (e.g. tokens) from one response and use them in the next request. Assert on status codes, JSON paths, or response time. If any step fails, you get an alert.
How do I get alerted when my API goes down?
Add alert contacts (email, Telegram, or webhook). When a check fails, SitePuls notifies your contacts immediately. You can also view incident history and response time graphs in the dashboard.
Can I monitor GraphQL or gRPC?
REST multi-step monitors target HTTP JSON APIs. If you can exercise an endpoint over HTTPS with standard requests, you can model it — dedicated GraphQL/gRPC clients are not required, but complex proprietary protocols may need a thin HTTP wrapper.
How is this different from logging and APM?
SitePuls runs synthetic checks from outside your app. Logs and APM show what happened inside services; synthetic checks prove what a client experiences and alert when those expectations break.
Can I assert on JSON fields?
Yes. REST monitors let you assert on JSON paths so a 200 with the wrong payload still fails the check.
What about rate limits?
Pick intervals that respect your API’s limits. SitePuls runs on a schedule; if you need sparse checks, choose a longer interval.
Do you store request bodies?
Configure the monitor with the headers and bodies you need for the check. Treat secrets like production credentials — rotate tokens used in monitors if they leak.