PagerDuty ready

FanHook for PagerDuty Webhooks

Verify PagerDuty v3 X-PagerDuty-Signature webhooks and fan out incident events to chat, status pages, and post-mortem tooling.

Start free with PagerDuty Read the docs

PagerDuty is the source of truth for incidents — but the v3 webhook format with rotating X-PagerDuty-Signature headers is annoying to verify in every consumer. FanHook handles signature rotation natively (multiple v1= candidates accepted) and forwards verified incident events to each public destination you configure.

Get incidents into Slack, into a status page updater, into your data warehouse, and into your own retrospective tooling — all from one signed feed instead of N copies of the same verification logic.

How it works

1
Create a PagerDuty sink in your FanHook dashboard and paste the secret PagerDuty showed when you registered the webhook subscription.
2
In PagerDuty → Integrations → Generic Webhooks (v3), add a subscription pointed at the ingest URL below.
3
Add fanout routes for incident chat channels, status pages, and any downstream automation.

Ingest URL

POST https://fanhook.xyz/ingest/<your-sink-id>

FanHook verifies each request's signature header against the PagerDuty webhook secret saved on your sink, stores the event, and fans out to every route you've configured.

Create your PagerDuty sink