Wire into anything
Trigger a runbook, open a ticket, flip a status page, or fan out to a channel we don't support natively — it's your endpoint.
Predictable JSON payload
Every event is a POST with title, message, and an ISO-8601 timestamp. Easy to parse, easy to route.
Safe by default
Requests are sent through an SSRF-guarded client that blocks private and metadata addresses, so a webhook can't be pointed at your internal network.
How to set up Webhooks alerts
What you'll need: A reachable HTTPS endpoint that returns a 2xx
- 1
Add your endpoint URL
In UptimeEye, open Notifications → New channel → Webhook and paste your HTTPS endpoint.
- 2
Handle the POST
On each event we send a JSON body (see below) and expect a 2xx response. Anything else is treated as a failed delivery.
- 3
Attach it to what you monitor
Add the channel to any monitor, cron job, SSL check, or status page — on every plan, including Free. Send a test alert to confirm it lands where your team actually looks.
Payload
POST https://your-endpoint.example.com/hooks/uptime
Content-Type: application/json
{
"title": "Monitor down: api.acme.com",
"message": "api.acme.com is not responding (checked from 3 regions).",
"timestamp": "2026-07-13T09:41:07Z"
}What triggers a Webhooks alert
Downtime & recovery
When a monitored website, API, or server goes down — confirmed from multiple regions — and again the moment it recovers.
SSL & domain expiry
Early warnings before a TLS certificate or domain expires, so you renew before it takes the site offline.
Cron & scheduled-task failures
Dead Man's Switch alerts when a scheduled job fails or misses its window, so silent background jobs never rot unnoticed.
Ways teams use it
- Kick off an automated runbook or self-healing script the instant a service fails.
- Open a ticket in a system UptimeEye doesn't integrate with directly.
- Forward events into your own logging, SIEM, or data pipeline.
Webhooks monitoring FAQ
What does the webhook payload look like?
A JSON POST with three fields: title, message, and an ISO-8601 timestamp. The same shape is used for down, recovery, SSL-expiry, and cron-failure events.
Can I point a webhook at an internal service?
No — and that's deliberate. Webhook requests go through an SSRF-guarded HTTP client that blocks private, loopback, and cloud-metadata addresses on every send and redirect.
What response do you expect?
Any 2xx status. A non-2xx response is treated as a failed delivery, so make sure your endpoint acknowledges quickly.
Is the webhook channel free?
Yes. Like every channel, custom webhooks are available on every plan, including the free tier.