StatusCake is a popular uptime monitoring platform with a generous free tier. It supports HTTP monitoring with customizable status codes and confirmation checks to reduce false positives. Alert24 healthcheck endpoints work with StatusCake's standard HTTP test type.

Before you start

You'll need:

An Alert24 API key (Settings → API Keys → Create API Key)
The ID of the check you want to monitor, found in Monitoring → [check name] or via the API

Create an uptime test

In StatusCake, go to Uptime Monitoring → New Uptime Test
Confirm Test Type is HTTP
Enter a Test Name (e.g. "Checkout Service — Alert24")

Paste your healthcheck URL into the Test URL field:

https://app.alert24.net/api/healthcheck/ak_live_YOUR_KEY/YOUR_CHECK_ID

Select Contact Groups to be notified on downtime
Leave Confirmation Tests at the default (2) to prevent false positives
Click Save test

StatusCake will confirm failures from two separate monitoring servers before alerting. When Alert24 reports a check as down, it returns 503, which StatusCake treats as a failure.

Org-wide test

To monitor all your active Alert24 checks:

https://app.alert24.net/api/healthcheck/ak_live_YOUR_KEY

Tips

Status codes: StatusCake's Status Codes field lists HTTP codes that trigger an alert. The default includes common error codes — 503 is covered. You don't need to change anything.
String matching: Not required. StatusCake can check for a keyword in the response body, but the HTTP status code approach is simpler and more reliable for this use case.
Timeout: The default 15-second timeout is more than sufficient for Alert24's edge-served endpoints.
Confirmation servers: Keeping this at 2 (the default) means both StatusCake monitoring servers must see a failure before you're alerted, which prevents notifications triggered by brief network blips rather than real outages.