Quick start guide
Get Started with WebhookWatch
Real-time webhook debugging for Dutch developers. Four steps from zero to inspecting live payloads.
Step-by-step setup
You'll have a working webhook endpoint in under three minutes. No server required, no tunneling tools to install.
Create your account
Sign up at webhookwatch.nl/register with your work email. You get three free channels immediately — for example hooks.webhookwatch.nl/ab42x91 — each with its own URL, log history, and replay controls.
Copy your webhook URL
Open the dashboard, click on any channel, and hit "Copy URL" next to the endpoint address. The URL includes a unique channel ID, so you can run multiple integrations side by side without cross-talk.
Paste it into your app
Drop the URL into your service's webhook settings — Stripe, Shopify, GitHub, Twilio, or a custom Node.js script. WebhookWatch accepts all standard POST payloads and returns a 200 OK instantly so your sender doesn't retry.
Inspect the logs
Switch back to the dashboard. Every incoming event appears live with headers, body, status code, and response time. Click any entry to expand the raw JSON, diff it against a previous payload, or replay it to a staging server.
See it in action
A quick walkthrough from account creation to your first captured webhook event.
00:00 — Sign up and grab your first channel URL
00:28 — Configure a Stripe test webhook
00:55 — Trigger a test charge and watch the payload arrive
01:20 — Expand headers, inspect the signed body
01:48 — Replay the event to localhost:3000
02:10 — Set up a filter to highlight failed deliveries
Full video available on our YouTube channel — search "WebhookWatch quick start" or visit youtube.com/webhookwatch.
What to do next
Once your first webhook is flowing, these features will save you hours of debugging.
Set up response templates
Return custom status codes and JSON bodies. Useful when a sender expects a specific acknowledgment — for example, returning {"status":"received"} with a 200 code so Stripe stops retrying.
Use payload filters
Highlight events that match a condition, like event.type == "charge.failed" or headers["x-signature"] is missing. Filters color-code your log so anomalies stand out immediately.
Forward to production
After verifying a payload locally, use the one-click forward button to send it to your staging or production endpoint. No need to reconstruct the request manually in Postman or curl.
Check delivery stats
The stats panel shows events per hour, average latency, and retry counts. If your Twilio webhooks suddenly spike from 12/hour to 340/hour, you'll see it in the chart before your SMS bill does.