Start here

Quick start

Four steps take you from an empty account to a webhook that arrives at your app. You only write code in the last one, and only if you want signed deliveries.

1. Create a source. Sign up and confirm your email with the 6-digit code. Open Sources, click Create source, give it a name such as stripe-prod and click Create. The source gets a unique ingest URL of the form https://app.webhooker.eu/in/<token>, shown in the Ingest URL column with a copy button.
2. Paste that URL into your provider's webhook settings: Stripe, GitHub, Shopify, or anything that sends an HTTP POST. To reject forged requests, open the source's Settings tab and turn on Authenticate inbound requests with the provider's preset and signing secret (see Inbound verification).
3. Add a destination. On the source's Destinations tab, click Add destination, choose Create new, enter a name and the URL on your side that should receive each event, then click Create & connect. The source and destination are linked straight away, and you can add more than one.
4. Optionally sign deliveries. In the same form, switch on Sign outbound requests and pick HMAC signature, so Webhooker signs every delivery. Then check the signature in your handler (see Verify our signature).

How do I send a test event?

Use your provider's own tooling, such as stripe trigger in the Stripe CLI or the ping event GitHub sends when you save a webhook, or post a request yourself. POST, PUT, PATCH and DELETE are accepted, with any content type, up to 1 MB.

curl -X POST https://app.webhooker.eu/in/YOUR_SOURCE_TOKEN \
  -H "Content-Type: application/json" \
  -d '{"event":"ping"}'
# HTTP/2 200
# {"status":"SUCCESS","message":"Request received successfully.","request_id":"…"}

Where do I see the event?

The source's Overview tab lists every event it received, with columns for delivery status, content type, size and verification result. Switch Live on in the header to watch events arrive as they come in. Click a row to open the event: the Body and Headers tabs show exactly what the provider sent, and the Deliveries tab shows every attempt with its status code, latency and time. A failed delivery has a Resend button.

What happens after your provider sends the first event?

Once your provider starts POSTing to the ingest URL, Webhooker verifies each request, stores it, and delivers it to every destination on the source. Each attempt waits 10 seconds for a response by default, adjustable per destination. If a destination is down, Webhooker makes up to six attempts over about five hours, then moves the delivery to the source's Dead letters tab, where you can replay it one by one or with Replay all. The ingest URL and retries and replay pages go a level deeper.

Troubleshooting

Create your first source

Last updated 15 September 2026