Test PagerDuty webhooks
PagerDuty sends webhooks for incident events such as triggered, acknowledged, escalated, and resolved, plus service created, updated, and deleted events. Capture them on a free webhooks.cc endpoint to see exactly what PagerDuty sends, then replay deliveries or forward them to your local handler.
No credit card · 50 requests/day free · or get a guest URL without an account
Prefer a walkthrough? Read the local webhook testing guide.
How to test PagerDuty webhooks
- 1
Create a webhook endpoint
Sign in free with GitHub, Google, or email to create a persistent endpoint, or grab an instant guest URL at webhooks.cc without an account.
- 2
Point PagerDuty at your URL
Paste the endpoint URL into PagerDuty: Integrations → Generic Webhooks (v3) → New Webhook, or the REST API (POST /webhook_subscriptions).
- 3
Inspect what arrives
Each delivery appears live in the dashboard with method, headers, body, query parameters, and source IP.
- 4
Forward to localhost or assert in CI
Run whk tunnel <port> to forward webhooks to a local server, or use the TypeScript, Python or Go SDK to wait for and assert on deliveries in tests.
PagerDuty webhook authentication
| Auth header | x-pagerduty-signature |
|---|---|
| Algorithm | HMAC-SHA256 |
| Verification in webhooks.cc | Capture deliveries to inspect raw signature material |
The value is v1={hex}, an HMAC of the raw body keyed with the secret PagerDuty returns when the subscription is created. During secret rotation the header carries several comma-separated v1 signatures; accept a match on any.
New to signature verification? Read the webhook signature verification guide.
Everything in one place
- Live dashboard: see deliveries the moment they arrive
- Forward to localhost with whk tunnel
- Replay any captured request to any URL
- Mock responses with custom status, headers, and body
- Forward to your servers, Slack or Discord
- TypeScript, Python and Go SDKs for CI assertions
- MCP server for AI coding agents
PagerDuty webhook questions
Create a free endpoint on webhooks.cc (sign in with GitHub, Google, or email, or use a guest endpoint without an account), then configure it as your webhook URL: Integrations → Generic Webhooks (v3) → New Webhook, or the REST API (POST /webhook_subscriptions). Every delivery shows up live in the dashboard with full headers, body, and query parameters. To hit a local server, run whk tunnel <port> and the CLI forwards each webhook to localhost.
Yes. Capture one real delivery from PagerDuty, then replay it to any URL from the dashboard, or run whk tunnel <port> to forward live deliveries to localhost. webhooks.cc has no built-in PagerDuty sample templates, but the Send button posts any payload and headers you paste in.
PagerDuty authenticates each delivery with the x-pagerduty-signature header (HMAC-SHA256). The value is v1={hex}, an HMAC of the raw body keyed with the secret PagerDuty returns when the subscription is created. During secret rotation the header carries several comma-separated v1 signatures; accept a match on any. Capture a real delivery on webhooks.cc to inspect the exact header value, then implement the check in your handler.
Yes. A free account gets you persistent endpoints, 50 requests per day, 7-day retention, and full CLI, SDK, and MCP access, with no credit card. You can also try a guest endpoint without an account: up to 25 requests for 12 hours.
More providers
Your PagerDuty webhook URL is seconds away
Sign up free, create an endpoint, and point PagerDuty at it.
No credit card · or try without an account