Send a request to try it
Point your provider (Stripe, GitHub, Slack…) at the endpoint above, or run this:
Headers
Body
Binary · base64| Form field | Value |
|---|---|
Query parameters
| Name | Value |
|---|---|
- Received
- From
- Size
- ID
About the Webhook Tester
The Webhook Tester gives you a unique URL that captures any HTTP request sent to it and shows it in your browser as it arrives. Each capture includes the method, path, query string, headers, body and sender IP. Use it to see what Stripe, GitHub or Slack sends before your endpoint exists, or to debug a signature check.
Any method and sub-path under /hook/<your-id> works. Bodies are captured up to 256 KB (anything longer is cut and marked truncated); binary bodies are shown as base64. You can forward a captured request to another URL, or auto-forward new ones as they arrive, while the inspector page is open.
How to use it
- Copy the endpoint URL. Bookmark the page to keep it.
- Paste it into your provider's webhook settings, or send a request with
curl. - Select a request to inspect its headers, body, query parameters or raw HTTP.
- Filter requests by method, path, header or body text.
- Replay a request with "Forward to", or copy it as
curl.
Examples
curl -X POST 'https://webmastertools.dev/hook/<your-id>/orders?source=curl' \
-H 'Content-Type: application/json' \
-d '{"event":"order.created","id":42}'
Common questions
How long are captured requests kept?
The latest 100 per URL, in server memory only. They are deleted when you click "Clear all", when the URL has had no requests and no viewers for 24 hours, or when the server restarts; if the inspector hits its memory limit, the least recently used URLs are cleared first.
Is my webhook URL private?
The ID is random and unguessable, but not password protected. Anyone with the URL can view what it captured, so avoid sending real secrets.
Can I forward webhooks to localhost?
No. Forwarding is done by our server, which blocks localhost and private network addresses, and only while this page is open. Use a publicly reachable URL.
Can I change the response the endpoint returns?
No. The endpoint always replies 200 with {"status":"received","id":"..."}.
Related tools
- HTTP Request Builder: send a crafted request to your real endpoint once it is live.
- JSON Formatter & Validator: clean up and validate a captured payload.
- SHA-256 & HMAC Hash Generator: recompute an HMAC signature to check it matches the header.