Examples / Monitoring and incidents / PagerDuty
PagerDuty webhooks
Incident triggered, acknowledged, escalated, resolved, and service or priority changes.
Events
- incident.triggered
- incident.acknowledged
- incident.resolved
- incident.priority_updated
Signature
Header X-PagerDuty-Signature with v1=<hex>, possibly several. HMAC-SHA256 of the raw body with the webhook subscription secret.
â A bin checks PagerDuty signatures: add the webhook subscription secret under Signature verification (PagerDuty).
Check a PagerDuty signature with the free tool (use the GitHub preset).
Retries
PagerDuty retries with backoff for a limited time and disables a subscription after repeated failures.
See a retry schedule in the calculator.
{
"event": {
"id": "01BRB6ZP4M6T8ZG4X6BP63ZB9P",
"event_type": "incident.triggered",
"resource_type": "incident",
"occurred_at": "2026-10-08T06:34:00.000Z",
"agent": { "type": "service_reference", "summary": "Shop API" },
"data": { "id": "PGR0VU2", "type": "incident", "title": "Webhook delivery failures above 5%", "status": "triggered", "urgency": "high", "service": { "summary": "Shop API" } }
}
}
- Drop the 'v1=' prefix and use the GitHub preset without 'sha256='.
Receive PagerDuty webhooks with webhooks.xyz
Create a bin. Paste its URL into PagerDuty. Each request shows at once with its headers and body. Add your secret, and each request gets a verified or failed mark. Add your server as a destination, and deliveries retry when it is down. Request an invite.