Webhooker
Documentation
Webhooker docs
Webhooker sits between the services that send you webhooks and the services on your side that need to hear about them. It gives every source one URL to receive on, checks that each event is genuine, saves it, and delivers it to your app with retries and a full log. This guide covers the two places you write code: sending events in, and confirming the ones we deliver.
How it works
Every event runs through the same four steps. You never manage the queue or the retries yourself, so most of what follows is background you can skim.
Receive
A provider POSTs to your source's ingest URL.
Verify
We check the provider's signature and reject forgeries.
Store
The event is written to durable storage before we ack.
Deliver
We forward it to your destinations, retrying until it lands.
You don't need to understand every step to get going. Create a source, paste its URL into your provider, point it at your app, and Webhooker handles the rest. The quick start walks through it in four steps.
A few words you'll see
- Source — one inbound stream. Each source has its own ingest URL and its own provider (Stripe, GitHub, Shopify, or anything that sends an HTTP POST).
- Destination — a URL on your side that should receive the events for a source. A source can fan out to more than one.
- Event — a single webhook that came in. It keeps a stable ID you can use to match an inbound event to every delivery attempt.
- Signing secret — an optional key on a destination. When it's set, Webhooker signs each delivery so your handler can confirm the request really came from us.
Where to go next
From zero to your first delivered event in four steps.
The ingest URLPOST events to your source and read the response codes.
Inbound verificationHow Webhooker checks a provider's signature before it accepts a payload.
Verify our signatureConfirm a delivery really came from Webhooker, in Node, Python, or Go.
Retries and replayWhat happens when your endpoint is down, and how to resend an event.
Meta / FacebookThe GET handshake for Facebook, Instagram, and WhatsApp, handled for you.
Background reading
These docs cover how Webhooker behaves. The blog covers the problems underneath it — useful whether or not you use us: how a webhook travels end to end, when a project needs a gateway, and the full webhook security model. All articles →