RequestBin alternatives for webhook testing (2026)

Ask five developers what "RequestBin" is and you'll get three different answers. The name has been attached to a beloved open-source project, a hosted service that changed hands, and at least one modern product trading on the same word. Before comparing alternatives, it's worth untangling which RequestBin you actually mean — because they have very different limits, and very different futures.

The original: open-source RequestBin

RequestBin started as an open-source project created by Jeff Lindsay and later maintained by Runscope. It gave you a URL that collected requests and let you inspect them in a human-friendly way — the original request bin, and the reason the term is generic now. The publicly hosted instance was discontinued: ongoing abuse made it impractical to keep running, which the maintainers stated plainly in the project README.

The code is still out there under the MIT license — a Python/Flask app with Redis behind it — and community forks keep it buildable with modern Docker images. Self-hosting is a legitimate choice when payloads can't leave your network: compliance requirements, air-gapped environments, or client work with strict data terms. The trade-off is that you're now running infrastructure in order to debug infrastructure. The codebase is old, maintenance is community-driven, and there is no hosted fallback if your instance falls over. If you go this route, keep it patched, put it behind authentication, and never expose it to the public internet unprotected — a request bin collects whatever strangers send it.

requestbin.com today: a redirect to Pipedream

For years the hosted RequestBin lived on at requestbin.com as part of Pipedream: visit, get a URL, inspect requests with headers and body. As of September 30, 2026, requestbin.com and pipedream.com/requestbin both redirect to Pipedream's homepage, so there is no standalone bin to open there anymore. If you had it bookmarked for quick checks, any of the bins below does the same job.

requestbin.net: same name, different company

Separately, requestbin.net is a modern hosted request-bin product with no connection to the original project (or to us, for that matter). Its free tier gives you a small number of bins with capped request history — enough to evaluate it properly. Paid plans, in the roughly $12–29/month range at the time of writing (check their pricing page), add unlimited history, request replay, forwarding rules that relay requests to your own app, and mock APIs. Of the three, it's the closest in spirit to "classic RequestBin, but maintained".

Why request bins keep disappearing

The original hosted RequestBin died of abuse, and it wasn't alone. A free, anonymous URL that accepts arbitrary POSTs is irresistible to spammers, malware operators, and people testing stolen cards; storage and moderation cost real money while the service earns nothing. That's why survivors in this space either cap the free tier hard, require accounts, or fold the bin into a larger paid platform. When you pick a bin, the business model is a durability signal: a tool with a plausible way to make money is a tool that still exists next year. It's also why webhooks.sh bins are anonymous but time-boxed to 48 hours — useful for a debugging session, useless as permanent abuse infrastructure.

What to look for in an alternative

• Longevity and maintenance. A debugging tool you paste into provider dashboards should not vanish mid-integration.
• Bin limits on the free tier. Request caps and history depth decide whether the free tier is usable for real work.
• Replay and forwarding. Inspecting is half the job; re-driving your handler is the other half.
• Signature tooling. Verifying HMACs is where webhook debugging usually gets stuck.
• Data handling. Who can see the bin, and how long does the data live?

The comparison

Features and pricing change fast; check each product's current pages before deciding.

Verdict

Self-host the open-source RequestBin if payloads legally cannot touch third-party infrastructure and you accept the maintenance burden that comes with a decade-old codebase.

Pick webhook.site if you want custom responses or 7-day URLs without signing up, and can live with its free cap of about 50 requests per URL; see our webhook.site comparison.

Pick requestbin.net if you want a classic bin with replay and forwarding available today and don't mind creating an account.

Pick webhooks.sh if you want the zero-friction version: a free bin at view.webhooks.page with no signup, requests landing live, and a browser-based HMAC verifier next to it for the signature step. When you need your own code in the loop, the local testing guide covers the pairing, and Solo ($12/month) adds persistent endpoints, replay, and a CLI that relays deliveries to localhost.