What is API monitoring?
API monitoring sends real requests to your endpoints on a schedule and checks the responses, the same way an app or a partner integration would. It tells you when an API is unreachable, slow, returns the wrong status code, or returns data your clients can't use.
Mobile apps, single-page frontends and integrations all depend on APIs, so an API failure usually looks like “the app is broken” to customers, even while your website loads fine. Watching the API directly finds the cause faster.
Assert on the response, not just the status code
An endpoint can return 200 with an error in the body, an empty list or a stale value. Spot Downtime reads the JSON response and checks the fields you care about: status equals “ok”, data.items.length greater than 0, error does not exist. Paths use dot or bracket notation, so nested values and list items are easy to reach.
Add up to 20 assertions per monitor and set the exact status code you expect, such as 201 for an endpoint that creates something. When an assertion fails, the alert names the field, the rule and the value that came back, for example: queue.depth should be less than 100 (got 412).
Authenticated and write endpoints
Send GET, POST, PUT, PATCH, DELETE or HEAD requests with up to 20 headers and a JSON or text body. That covers bearer tokens, API keys and health endpoints that expect a POST. Use a dedicated read-only key where you can, because headers are visible to everyone in the workspace.
HTTPS API monitors also track the certificate's expiry and warn 14, 7 and 1 day ahead, and failures are confirmed from more than one region before anyone is alerted. Add cron job monitoring for background work, and a status page to keep the people who use your API informed.

