Alerts & notifications
Webhooks
JSON event delivery to your own endpoint: payloads, events, and semantics.
Enable the webhook channel in a monitor's Settings under Alerts, paste an http(s) endpoint URL, and pick the events to forward. Every event is one JSON POST:
Example delivery
{
"event": "monitor.down",
"timestamp": "2026-08-07T09:14:03.201Z",
"monitor": {
"id": "3dcb8ffc-f9e4-45b7-a787-bd2b1615671a",
"name": "API",
"url": "https://api.example.com/health",
"type": "api",
"status": "down"
},
"detail": "HTTP 500"
}| Event | Fired when |
|---|---|
monitor.down | The monitor goes down |
monitor.recovered | It comes back up after an outage |
monitor.degraded | Responses stay over the degraded threshold |
monitor.degraded_recovered | Response times return to normal |
monitor.ssl_expiring | The SSL certificate enters its warning window |
monitor.domain_expiring | The domain registration is 30 days from expiry |
- Requests are sent with
content-type: application/jsonand user agentUptimixWebhook/1.0. - Delivery times out after 10 seconds; there are no automatic retries.
- Any status under 400 counts as delivered; deliveries are recorded in the audit log.
- Expiry events additionally carry
daysRemainingandexpiresAt.
Recovery events follow the same incident-based rule as every channel: your endpoint only receives monitor.recovered for an outage it was told about. See Alert logic & recovery.