Only need to know a website or endpoint is up? Uptime monitoring
API monitoring shares locations, alert channels and status pages with everything else in your account.
Uptime Monitoring · Synthetic Monitoring · Cron Job Monitoring · SSL Monitoring · Status Pages · Monitoring as Code
Five popular API monitoring platforms compared on what teams actually evaluate: check frequency, multi-step request flows, free tier, check locations and alerting integrations. Competitor details as published on each vendor's website, October 2026.
| Capability | LoadFocus | Pingdom | UptimeRobot | Datadog | New Relic |
|---|---|---|---|---|---|
| Minimum check frequency | 60 seconds | 60 seconds | 15 seconds | 60 seconds | 60 seconds |
| Multi-step / chained API flows | Yes, login + token + call (paid plans) | Browser transactions | Not listed | Yes (Synthetic API) | Yes (scripted API monitor) |
| Free tier with API checks | Yes. 10 checks and 10,000 runs a month free | Trial only | 50 monitors / 5 min | Trial only | Yes. 500 checks/mo free |
| Global check locations | 25 AWS regions | 100+ | 4 regions | 29 | 20 |
| Alert integrations (Slack, PagerDuty, webhook) | Yes, all three (PagerDuty on paid) | Yes | Yes (PagerDuty on Team) | Yes | Yes |
Uptime alone misses degraded performance. These four metrics tell you whether your APIs are actually healthy, not just reachable.
Time the slowest 5% of requests take. Averages hide the long tail; p95 exposes it. A p95 over 500 ms on a payment API means real users are waiting longer than they tolerate, and not all are coming back.
How long the API takes to send the first byte after the request hits. Catches DNS, TLS, and server-processing slowdowns separately from network transfer time. Spikes here usually point at the origin, not the client network.
Percentage of synthetic checks that pass (correct status code + response shape + within latency budget). Drops below 99% on a production API are an alertable incident, not a curiosity.
Synthetic checks tell you the API is up; RUM tells you whether real customers experienced the same. Pair both, synthetic alerts you to outages, RUM tells you the customer impact.
Production APIs that drive revenue or block other systems: every minute. Internal or low-criticality APIs: every 5 minutes is enough.
Uptime monitoring just checks if the endpoint responds. API monitoring also validates status codes, response body shape, latency budgets, and chained workflows (login → token → call). API monitoring catches the silent breakages uptime monitoring misses.
Yes. LoadFocus supports headers, OAuth bearer tokens, and chained requests where one step's response (a token) becomes the next step's auth. No need to expose a service account password in plain config.
Within one check interval. With 1-minute checks and Slack/PagerDuty alerts, your on-call gets paged within about a minute. Configure alert thresholds to require 2 consecutive failures to suppress single-region transients.
Yes. GraphQL is just a POST with a JSON body, fully supported. gRPC requires a small adapter (gRPC-Web or curl over h2), most teams wrap it in a thin REST proxy purely for monitoring.
Plans are priced by checks and monthly runs, and every run from every location counts. Free has 10 checks and 10,000 runs a month at 5-minute frequency, which covers one check every 5 minutes from one region. Starter has 25 checks and 25,000 runs at 1-minute frequency, and Professional 75 checks and 100,000 runs at 1-minute frequency. The pricing page lists current prices in your currency.
API monitoring continuously sends real requests to your API endpoints and checks that they respond, return the correct status code and data, and stay fast. It catches outages, slowdowns and broken responses before your users do, and alerts you the moment something breaks.
Yes. LoadFocus has a free tier for API monitoring: scheduled checks from multiple cloud regions with alerts on failures and SSL expiry, no credit card required. You can also run an instant one-off check from any browser with the free multi-region API status checker.
API performance monitoring tracks how fast your endpoints respond over time, breaking each request into DNS, connection, TLS, time to first byte and download. It surfaces latency regressions and regional slowdowns so you can fix them before they cost conversions.
Yes. LoadFocus generates one API monitor per operation from an OpenAPI 3.x or Swagger 2.0 spec, in JSON or YAML. Paste the spec or point LoadFocus at its URL, pick a frequency, and every endpoint is monitored in a single step with your plan limits applied.
Yes. API monitors support setup and teardown scripts: a setup script runs before the request (fetch an OAuth token, sign the request, build a unique payload) and a teardown script runs after the response (clean up created data, scrub logs). Scripts run sandboxed with got, axios, crypto and faker available, and can read your stored secrets.
Everything on this page is scriptable. Manage monitors from your terminal, wire checks into CI, or let your AI assistant create and read them for you.
Connect Claude, Cursor or any MCP client to LoadFocus and create monitors, run checks and read results straight from your AI assistant. One command to set up, OAuth or API key auth.
Define monitors in YAML and deploy them with npx @loadfocus/monitoring from your terminal or CI pipeline. Version-controlled, reviewable and repeatable across environments.
Step-by-step guides for API checks, multistep flows, TCP, DNS and heartbeat monitors, alert channels, status pages and SLA reports.
Your API key, team ID and copy-paste setup snippets for the CLI and the MCP server live on the Developers page inside the monitoring dashboard.
In-depth guides on the same topic from the LoadFocus blog.
Guides for building API checks, chaining steps, using variables and reading the results.
Product news, test locations, IPs to whitelist and white-label reports.
