Webhook Library
The Webhook Library is a catalog of real provider payloads you can send to a Source URL on demand.
It exists because triggering a genuine webhook is often the slowest part of building against one. Seeing an inbound SMS event usually means sending yourself a text message and waiting for it to arrive. The library sends you the same payload immediately.
Sending a sample payload
The library is on the home page and on any Source URL that hasn't captured anything yet. Once requests have arrived, open it with Test webhook above the request list.
- Pick a platform. The filter above the list narrows it by name.
- Pick an event type. Platforms publish many, so the second filter narrows those.
- Choose Send test.
The payload arrives at your Source URL and appears in the request list like any other request. If the Source URL has a Source Type, the library shows only that platform's samples. On a platform's page, such as inspect.hookdeck.com/webhooks/stripe, it opens on that platform.
Your browser sends the sample as a POST, with the sample's headers and body. So the captured request also carries a few headers your browser adds, and lacks any header browsers don't let a page set.
What the samples contain
Samples mirror the shape of real provider events: the same field names, nesting, and header conventions. They're representative, not live, so identifiers and timestamps are sample values rather than references to real objects in your account.
That's usually what you want when you're writing parsing and routing logic. Samples aren't signed with your signing secret, though, so they won't pass a signature check. When you need a signature your code can genuinely verify, send a real event from the provider's own dashboard instead.
Contributing
The dataset is open source at hookdeck/webhook-samples. If a provider or event type you need is missing, adding it is a pull request.
For deeper, provider-specific guidance on handling these events in code, see the webhook skills directory.