Use Alert24 Healthcheck Endpoints with Any Uptime Monitor

Alert24 exposes healthcheck endpoints that return 200 OK when your monitored checks are up and 503 Service Unavailable when they're down. This makes Alert24 compatible with any uptime monitoring tool that evaluates HTTP status codes — no JSON parsing or custom configuration required.

Why use these endpoints

Most teams already have a monitoring tool they trust for uptime alerting (UptimeRobot, Pingdom, Datadog, etc.). Rather than replacing those tools, Alert24's healthcheck endpoints let you plug Alert24's monitoring results directly into your existing workflow.

The endpoints serve cached status — they don't trigger new check runs and don't consume check credits.

Available endpoint formats

# Single check
GET https://app.alert24.net/api/healthcheck/{apiKey}/{checkId}

# All checks (org-wide)  
GET https://app.alert24.net/api/healthcheck/{apiKey}

• 200 = check is up
• 503 = check is down or degraded
• X-Alert24-Checked-At header shows when the last real check ran

See the Healthcheck Endpoints reference for the full response format.

Setup guides by tool

Finding your check ID

In Alert24, go to Monitoring → [check name] — the check ID is in the URL. Or retrieve it via the API:

curl https://app.alert24.net/api/v1/monitoring \
  -H "Authorization: Bearer ak_live_YOUR_KEY"

Rate limits

Healthcheck endpoints share the standard read rate limit: 60 requests per minute per API key. For monitors polling faster than once per minute, create a dedicated API key.

Note on dependency

These endpoints depend on Alert24 being operational. If Alert24 is unreachable, a third-party monitor will report a failure — which could be misleading if Alert24 itself is the problem. Use healthcheck endpoints as a convenience layer on top of Alert24's direct alerting, not a replacement for it.