features · http(s) checks
API monitoring tool that catches broken contracts, not just downtime
An API monitoring tool calls your endpoints on a schedule and alerts you when the response is wrong. AlertPing runs HTTP(S) checks every 30 seconds and asserts on status code, body keywords, JSON values and response time.
get · post · head · custom headers · auth
alertping ▸ check: orders-api
every 30 s
# check config
GET https://api.acme.dev/v1/orders
header Authorization: Bearer ••••••••
assert status == 200
assert body contains "orders"
assert json $.status == "ok"
assert response_time < 800 ms
# last run · 07:14:32 UTC
FRA 200 212 ms 4/4 assertions pass
IAD 200 118 ms 4/4 assertions pass
SIN 200 301 ms 4/4 assertions pass
verdict UP · next run in 30 s▌
assertions
A 200 that returns garbage is still an outage
Plenty of APIs fail politely: status 200, empty payload, wrong data. Simple up/down checks miss all of it. Assertions treat the response like a contract and page you the moment any clause breaks.
status code
Exact or range
Expect 200, any 2xx, or even a specific 301 if that is the contract. Anything else fails the check.
keyword match
Body must contain it
Require a string in the response, or require its absence: "error", "maintenance", an empty cart where products should be.
json path
Assert on real values
Point at a path like $.data.items[0].price and assert equals, exists, greater than. Schema drift pages you before customers file bugs.
response-time budget
Slow is the new down
Set a millisecond budget per check. Blow it from all three regions and the check fails, even with a perfect 200. Latency is charted per region so you can see whether Singapore got slow or everything did. The same budget logic backs our website monitoring tool.
auth headers
Monitor endpoints behind auth
Bearer tokens, API keys, basic auth, any custom header. Secrets are stored encrypted and never appear in logs or alerts.
when it breaks
One failed assertion, three regions, one page
A failed assertion triggers instant re-checks from Frankfurt, Virginia and Singapore. When 3 of 3 agree, downtime alerts fire by SMS, email, Slack and webhook in under 10 seconds, with the exact assertion that failed and the response we saw. No guessing from a generic "check failed".
HTTPS endpoints get certificate checks alongside, so an expiring cert never takes the API down silently: see SSL certificate monitoring. New to external checks? The setup walkthrough in how to monitor website uptime applies to APIs too.
example failure alert
● FAIL orders-api
assert json $.status == "ok"
got: "degraded" · 3/3 regions
incident #5023 · 07:15:04 UTC
The alert carries the failing assertion and the actual value, so on-call starts with the answer, not the question.
api check questions
Common questions
Can I monitor authenticated endpoints?
Yes. Attach bearer tokens, API keys, basic auth or any custom header to a check. Secrets are stored encrypted, masked in the UI, and never included in alert messages or logs.
What HTTP methods and assertions are supported?
GET, POST and HEAD with custom headers and request bodies. Assertions cover status code (exact or range), keyword presence or absence, JSON path comparisons, and a response-time budget in milliseconds.
How fast will I know when an assertion fails?
Checks run every 30 seconds. A failure triggers instant re-checks from all three regions, and on 3-of-3 confirmation the alert reaches you in under 10 seconds with the failing assertion attached.
Put your API contract under watch
HTTP(S) checks every 30 seconds with status, keyword, JSON and latency assertions. The first check runs in under a minute.