Account

What new tool do you want?

Developer Tools

Webhook Tester (Request Bin)

Get a unique URL that captures every HTTP request sent to it — method, path, query, headers and body — to debug webhooks from Stripe, GitHub, Shopify, Zapier and more.

How to use

  1. 1Create your webhook URL.
  2. 2Paste it into the service you're testing (or send a request with curl).
  3. 3Watch requests appear live and inspect headers and body.

Frequently asked questions

How long does the URL last?

24 hours, keeping the last 50 requests (up to 1,000 in total).

Is it private?

Anyone who knows the URL can send to it, and it's hard to guess. Don't use it with real customer data. Cookies and Authorization headers are never stored.

What does it reply?

HTTP 200 with {"ok":true}, so senders treat delivery as successful.

A real public endpoint, polled rather than pushed

Creating a bin issues an actual URL that accepts any HTTP method on any path beneath it and replies 200 {"ok":true}, so senders (Stripe, GitHub, Shopify, Zapier, or your own curl command) see a normal successful delivery. The UI itself doesn't hold a live connection to the server — it polls for new requests every 3 seconds while the tab is visible, which is simple and reliable but means a request can take up to ~3 seconds to appear on screen even though it was received instantly.

What's captured, and what's deliberately dropped

Method, path, query string, headers and body are all stored and shown, with JSON and form-urlencoded bodies pretty-printed automatically for readability. Two categories are stripped before anything is saved: Authorization headers and cookies, specifically so a real API key or session token pasted into a webhook config by accident doesn't end up sitting in a tool anyone with the URL can view. Bodies are capped at 64 KB (larger ones are flagged as truncated), and the bin itself expires after 24 hours, keeping the most recent 50 of up to 1,000 total requests.

Worked example: posting JSON with curl

After creating a URL, the tool shows a ready-to-run command: curl -X POST <url> -H "Content-Type: application/json" -d '{"hello":"world"}'. Running that from a terminal, the request shows up in the list within a few seconds as POST / with the body pretty-printed on two indented lines as "hello": "world", and a header entry content-type: application/json visible in the headers panel — the same view you'd use to confirm a real webhook from, say, a Stripe payment_intent.succeeded event is arriving with the payload shape your code expects, before wiring up a real handler.

Where it fits next to ngrok

A local tunnel like ngrok forwards requests into your own running server, so you can set a breakpoint and step through your handler — the right tool once you're writing the integration. This tool doesn't run any of your code at all; it just records what arrived, which is faster for the earlier question of 'what does this webhook actually send me' before you've written anything to receive it.

Why requests stop appearing if you leave the tab in the background

Polling explicitly checks document.hidden before each fetch and skips the request entirely while the tab isn't in focus, so switching away to configure the sending service and coming back later won't show a gap in the timeline — it'll simply catch up with everything that arrived once you return and the next 3-second poll fires. That's a deliberate trade-off against holding an open connection just to refresh a list a human is watching; it does mean a request can sit unseen for the entire time the tab is backgrounded, which matters if you're trying to time a webhook's arrival precisely.

Form-encoded and JSON bodies get decoded differently

A body sent with Content-Type: application/x-www-form-urlencoded is parsed with URLSearchParams and rewritten one field per line as key = value, while a JSON body (or anything starting with { or [) is parsed and re-serialized with two-space indentation — both transformations exist purely for on-screen readability, and if either parse fails, the raw, unmodified body is shown instead rather than a decoding error. A Stripe or GitHub webhook payload, which is JSON, pretty-prints cleanly; a classic HTML form POST, which is form-urlencoded, shows as a readable list of fields instead of one long ampersand-joined query string.

Related tools

More: Developer Tools