Webhooks Overview
Webhooks let AlertifyPro push real-time events to your own systems the moment something happens — no polling required.
How webhooks work​
AlertifyPro detects event
↓
Sends POST request to your endpoint
↓
Your server responds with 2xx
↓
Event logged as delivered
If your endpoint is unavailable, AlertifyPro retries with exponential backoff.
Creating a webhook​
- Go to Settings → Webhooks → New Webhook
- Enter your endpoint URL (must be HTTPS)
- Choose which events to subscribe to
- Copy the Signing Secret — use it to verify payloads
- Save and click "Send test event"
Available events​
| Category | Events |
|---|---|
| Monitors | monitor.down, monitor.degraded, monitor.recovered |
| Incidents | incident.created, incident.updated, incident.resolved |
| SSL | ssl.expiring, ssl.expired, ssl.changed |
| Heartbeat | heartbeat.missed, heartbeat.recovered |
| Maintenance | maintenance.started, maintenance.ended |
| Team | member.invited, member.removed |
Payload format​
All webhook payloads include:
{
"id": "del_uuid123",
"event": "monitor.down",
"timestamp": "2026-03-02T14:23:00Z",
"organization": { "id": "org_abc", "name": "Acme Inc." },
"data": { ... } // Event-specific payload
}
See Webhook Events → for the full payload for each event type.
Verifying signatures​
Always verify that webhook requests come from AlertifyPro by checking the HMAC signature:
X-AlertifyPro-Signature: sha256=<hmac>
See Webhook Signatures → for verification code examples in multiple languages.
Delivery logs​
View every webhook delivery attempt in Settings → Webhooks → Delivery Logs:
- Timestamp
- Event type
- HTTP status code returned by your server
- Response body (first 500 chars)
- Whether it succeeded or was retried