RequestBin alternatives that still work

If you just landed here from an old blog post or Stack Overflow answer telling you to "create a RequestBin": the original requestb.in shut down in 2018 (public bins were abused, and the maintainers pulled the plug). The name lives on in a few places, which causes confusion. Here's the current landscape, honestly.

What happened to RequestBin

What you actually wanted

A URL you can point anything at — a webhook provider, an sdk, a curl command, a suspicious IoT device — and then look at exactly what was sent: method, headers, query, body. Ideally without creating an account first. Your current options:

1. webhook.site

Good: mature, well known, instant URL with no signup.
Trade-offs: the free tier is tight — around 100 requests per bin, short expiry, and most of the useful features (custom URLs, forwarding/replay to your own endpoint, longer retention, CLI) are behind a paid plan. Fine for a two-minute look, frustrating for a real debugging session.

2. Self-hosting (RequestBin fork, or roll your own)

Good: full control, data never leaves your infra — the right call for regulated environments.
Trade-offs: you now maintain a service in order to debug a service. For "I need to see this payload in the next 90 seconds", it's the slow path.

3. CatchHook (this site)

CatchHook is a free request bin built to be what requestb.in was, plus the things you'd inevitably hit the paywall for elsewhere:

$ curl https://catchhook.catchhook.workers.dev/new        # instant bin, no signup — or click the button below

Trade-offs, honestly: the live view is polling-based (captures appear within a couple of seconds, not instantly-streamed), and it's hosted-only — if your payloads can't leave your network, self-host a fork instead.

Quick chooser

No signup needed. Or from your terminal: curl https://catchhook.catchhook.workers.dev/new

← All guides · Docs · CatchHook vs webhook.site