What is a webhook receiver and when is it useful?
Click "Create new URL" and you get a unique address like `https://yourdevtools.pro/api/webhook/abc12345`. Paste it into Stripe, GitHub, Zapier, Slack or anywhere else, and every incoming HTTP request shows up here in real time - method, headers, body, query, IP, country.
It's a great tool for debugging webhooks before you ship anything. Instead of deploying code and waiting for Stripe to send something, you can inspect the exact payload on our page and know what to expect.
Webhooks are ephemeral - they live for 24 hours, the last 100 requests are kept, then they're gone. We don't read their content.
How to use it
- Click "Create new URL", you get an address + a QR code to scan from your phone (handy for mobile testing).
- Copy the URL and paste it wherever the webhook should land (Stripe Dashboard, GitHub Settings → Webhooks, Zapier, your own script).
- Send a test request. Easiest is `curl -X POST {URL} -d '{"test": true}'` from a terminal, or the "Test" button in your webhook provider's panel.
- Logs appear in real time (we poll the server every 2 seconds). Expand any entry to see headers + body + query.
- Filter by method (GET / POST / PUT / DELETE), clear the list with "Clear logs", or mint a brand new URL.
When this is useful
Six typical scenarios where a webhook receiver saves hours of debugging:
- Debugging Stripe / PayPal webhooks. Plug our URL into the test panel, click "send test event", and see exactly what the payload looks like (event type, customer id, metadata).
- GitHub webhooks. Check the payload for push / pull_request / issue events without standing up a server.
- Zapier / Make / n8n integration testing. Drop our URL as the "trigger webhook" and inspect what your automation sends.
- Mobile app development. Your app fires analytics events? Point them at our URL and verify the JSON shape without touching the server.
- CI/CD callback debugging. Your pipeline POSTs after deploy? Plug our URL in to confirm the call actually goes through.
- Learning HTTP. See exactly what a real HTTP request looks like - all the headers, User-Agent, Content-Type, body.
Other HTTP-adjacent tools you might want: UUID generator (correlation ids), JWT decoder, regex tester.