A webhook receives alerts only after a Send Test to it succeeds. If you change the URL, alerts pause until another test to the new URL succeeds.
Set up a webhook
1
Open Destinations
Go to Destinations in the sidebar, click Add Destination, then choose Webhook.
2
Configure the webhook
The URL must be publicly reachable.
localhost and private IP ranges are rejected. Use HTTPS in production.3
Choose events
Select which events trigger this webhook. All six are enabled by default; at least one must stay enabled.
4
Copy your signing secret
Open the integration and reveal Signing secret (
whsec_…). Store it in your
receiving application — you need it to verify incoming requests.5
Send a test
Choose Send Test on the destination. UptimeIO sends a signed sample request to your URL, using your method and custom headers just like a real alert, and the destination starts receiving alerts once your endpoint answers with a 2xx status. Each destination can send 10 tests per hour.
Webhook payload
Every UptimeIO webhook has the same body shape, regardless of which event fired:incident.started_at can be null on recovery events. UptimeIO sends null
rather than substituting the resolution time, so that a null is never mistaken
for an incident that began the instant it ended. Treat started_at as optional.Event types
Example: monitor.auto_paused
incident is null for this event. subject and message carry the explanation;
resume the monitor from your dashboard to start checking again.
New event types may be added in future. Ignore events you do not recognise
rather than rejecting the request.
Headers
Every request includes:Verify the signature
The signature is an HMAC-SHA256 over the string{timestamp}.{raw request body},
keyed with your endpoint’s signing secret, hex-encoded and prefixed with sha256=.
Rotate the secret
Open the destination and choose Rotate secret. The previous secret stops working immediately, so have your receiving application ready to switch: verification fails between rotation and deployment.Custom headers
Add authentication or custom metadata as a JSON object:Custom headers cannot override
Content-Type or any X-UptimeIO-* header;
those are set by UptimeIO and take precedence.Troubleshooting
Next steps
Notifications overview
Assign webhooks directly to monitors
Events
Choose which events trigger notifications
Start monitoring free
Create a free UptimeIO account and set up your first monitor in minutes.