Can I monitor authenticated API endpoints?

Yes. API monitors support custom request headers, so you can send bearer tokens or API keys, plus request bodies for POST/PUT/PATCH endpoints.

How is API monitoring different from website monitoring?

Mechanically it's the same engine — the difference is control: you define the method, headers, body, acceptable status codes and body assertions instead of just checking that a page loads.

Can Moonitor detect an API that responds but returns errors?

Yes — expected status codes catch wrong responses, and keyword assertions catch error payloads that arrive with a 200.

How often can an API be checked?

Down to every 30 seconds on Team and Max plans, with response-time history kept for every check.

Part of every Moonitor plan

API monitoring that checks more than "is it up"

An API can be "up" and still broken: returning 500s on one route, answering with an error payload, or slowing from 80ms to 8 seconds. Load balancers and status pages won't catch that — a monitor that makes real requests and inspects real responses will.

Moonitor's API monitoring sends the exact request you configure — method, headers, body — and verifies the response: status codes you expect, keywords that must (or must not) appear, and how long it took, on every check.

Start monitoring See all features

7-day free trial — no credit card.

How it works

Describe the request
Choose GET, HEAD, POST, PUT, PATCH or DELETE, add request headers (auth tokens included) and a request body where needed.
Define a healthy response
Set the status codes that count as success and, optionally, a keyword assertion — a string that must exist or must not exist in the body.
Watch latency, not just uptime
Response time is recorded on every check, so a slow slide toward timeout is visible days before users complain.
Alert on real failures
Wrong status, failed assertion or timeout — verified from a second country — opens an incident and alerts your team instantly.

What you get

Full request control

Any HTTP method, up to 50 custom headers, and request bodies — enough to exercise authenticated endpoints and webhooks.

Expected status codes

Define exactly which status codes are healthy for each endpoint; anything else is a failure.

Keyword assertions

Catch soft failures by asserting a string appears — or never appears — in the response body.

Latency history

Per-check response times charted over time, so performance regressions are caught early.

Verified before alerting

Every failure is reproduced from a second country before you're paged — an egress hiccup near our checker never becomes your 3am.

Monitoring as code

Create and update API monitors through Moonitor's own REST API, so every new service ships with its monitor.

Frequently asked questions

Can I monitor authenticated API endpoints?: Yes. API monitors support custom request headers, so you can send bearer tokens or API keys, plus request bodies for POST/PUT/PATCH endpoints.
How is API monitoring different from website monitoring?: Mechanically it's the same engine — the difference is control: you define the method, headers, body, acceptable status codes and body assertions instead of just checking that a page loads.
Can Moonitor detect an API that responds but returns errors?: Yes — expected status codes catch wrong responses, and keyword assertions catch error payloads that arrive with a 200.
How often can an API be checked?: Down to every 30 seconds on Team and Max plans, with response-time history kept for every check.

Every failure verified before you’re alerted

Moonitor re-runs every failing check from a second country before opening an incident — so a network wobble near one checker never becomes a false alarm on your phone. Explore the full feature set, read the docs, or automate it all with the API.

Get started