Post a confirmed outage
The request goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with your own webhook.
For everything that is not on this page. A JSON payload to any HTTP endpoint, shaped, signed and filtered the way your system expects it.
What lands at your endpoint
This is the open channel, so the list runs longer on control than the others. Everything the alert pipeline sends to your endpoint is here, and nothing beyond it.
Post the recovery
The same endpoint receives the all clear, carrying the resolve time so your side can close what it opened.
Send the body you define
Without a template the full event goes out as JSON; with one, your own shape is rendered from site, customer, error and timing values.
Send only what matches
Conditions on any field of the payload decide whether a request leaves at all, so a low-tier client never reaches your paging endpoint.
Sign the request
With a secret set, the body is signed with HMAC SHA-256 and the signature travels in its own header, so your side can verify the sender.
Add your own headers
Any header you configure is merged into the request, which is how an API key or a tenant id reaches an endpoint that needs one.
Decide what counts as delivered
The accepted status codes and the timeout are yours to set, so an endpoint that answers 202 after twenty seconds is still a success.
Retry a failed delivery
A rejected or timed out request is retried on its own ladder, with every attempt recorded under History & Logs → Alerts.
Refuse an unsafe target
The URL is resolved and checked against internal and loopback targets before every send, and the signing secret is stored encrypted.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
Endpoint URL
hooks.yourcompany.com/uptimeifySecret stored encrypted
1. Point it at your endpoint
Add the URL that should receive the events, and a secret if you want the requests signed.
2. Shape the body
Leave the payload as it is, or write a template so the request arrives in the shape your system already reads.
3. Assign monitors and test
Assign the monitors the channel covers and send the test request, so the first real alert is not the first delivery attempt.
Before you point a webhook at your endpoint.
Set a secret. The body is then signed with HMAC SHA-256 and the signature travels in its own header, together with the algorithm, so your side can recompute it before trusting anything.
Yes. Without a template the full event goes out as JSON. With one, your own shape is rendered from the site, customer, error and timing values, so no adapter is needed on your side.
Yes. Conditions on any field of the payload decide whether a request leaves at all, which is how a low-tier client can be kept away from a paging endpoint.
The status codes you accept, 200, 201, 202 and 204 unless you change them, within the timeout you set. Anything else is a failure and goes on the retry ladder.
No. The URL is resolved and checked against internal and loopback targets before every send, so a webhook cannot be used to reach into a private network.
Every alert, in the shape your system already understands.
Point a webhook at your own endpoint, and every confirmed outage arrives in the shape your system already understands.