A request bin for webhooks and HTTP requests
By the HookWatcher team · Updated
What a request bin is
The name comes from the original RequestBin project: a URL that "catches" requests into a bin you can look through. The idea is simple and still the quickest way to answer questions such as:
- Does this provider send JSON or form data? Which headers?
- Does my HTTP client really send the
Authorizationheader I configured? - What does this no-code tool's "HTTP request" step put in the body?
- Is the retry logic in my outbound webhook sender working?
Get a URL
Open the playground. It creates an endpoint right away, with no account, and shows its URL in the form https://hookwatcher.com/<endpoint-id>. Requests appear in the page as they arrive. Without an account, an endpoint keeps the last 100 requests for 2 days; sign in to keep endpoints under your account, with the history your plan includes (see pricing).
Try it: your request bin
Live, on a real endpointSend it requests
GET, HEAD, POST, PUT, PATCH, DELETE and OPTIONS are captured, on any sub-path such as /<endpoint-id>/any/nested/path. A few useful commands (replace the placeholder with your endpoint ID):
curl -X POST https://hookwatcher.com/<endpoint-id>/orders \
-H 'Content-Type: application/json' \
-d '{"order_id":"ord_1042","status":"paid"}'curl -X POST https://hookwatcher.com/<endpoint-id> \ --data-urlencode 'text=hello world' \ --data-urlencode 'user_name=ada'
curl -X POST https://hookwatcher.com/<endpoint-id>/upload \ -F 'note=invoice for March' \ -F 'file=@invoice.pdf'
curl 'https://hookwatcher.com/<endpoint-id>/callback?status=ok&tag=a&tag=b' \ -H 'X-Request-Id: 7f3c1e'
await fetch("https://hookwatcher.com/<endpoint-id>/events", {
method: "PUT",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ id: 1, name: "test" }),
});The raw query string is stored unchanged, so repeated parameters (tag=a&tag=b) keep both values, in order, when a request is forwarded or replayed; the Query tab lists each name once, with its last value. Form bodies are shown as fields and multipart parts with their names and file names; binary bodies are kept byte for byte, with a hex view in the replay tools.
What senders get back
curl -i -X DELETE https://hookwatcher.com/<endpoint-id>/items/9
HTTP/1.1 200 OK
content-type: application/json
{
"received": true,
"method": "DELETE",
"bodySize": 0
}What a request bin can't do (and what to use instead)
| You need | Why a bin isn't enough | Use |
|---|---|---|
| Your own code to handle the request | A bin answers by itself; your handler never runs | hwcli listen or forwarding |
| The provider to see your app's response | The sender gets the bin's response | An HTTPS tunnel |
| To run the same request again | Re-triggering the provider is slow and sometimes impossible | Replay |
| A permanent URL and history | Anonymous endpoints are short-lived | A free account |
Be careful with real secrets and customer data in any request bin. A HookWatcher anonymous endpoint's requests are visible only in the browser session that created it, and credential headers are masked in the inspector, but the safest habit is test-mode credentials until you have a signed-in workspace whose access is limited to its members.
Get your request bin URL
Frequently asked questions
Is RequestBin still available?
The original open-source RequestBin public service was shut down years ago; the name now refers to several hosted tools and to the general idea. HookWatcher's playground is one: a free URL that records requests, plus forwarding, replay and local delivery when you need more.
Can I use a request bin with webhooks that need verification?
If the provider just sends events, yes. If it first sends a challenge your app must echo back (Slack's URL verification, for example), the bin's default response won't pass; use a tunnel to your app for that step.
Does the bin change my request?
No. The body is stored byte for byte with a SHA-256 fingerprint. Formatting, such as a JSON tree, is only a view.
Can I get notified when a request arrives?
The playground updates live while it's open. Signed-in workspaces show a live stream across endpoints and can forward each request on to your own URLs.