webhook.site alternatives

webhook.site is the best-known request inspector, and for a quick "what does this payload look like" check it's perfectly fine. People go looking for an alternative for one of a few concrete reasons:

• The free limits — roughly 100 requests per URL and short expiry. One misbehaving integration that retries (Stripe retries for days) burns through that mid-session.
• The paywall placement — the features you reach for while debugging are the paid ones: replaying/forwarding a capture to your real endpoint, custom URL aliases, the CLI, longer retention.
• Binary payloads — non-text bodies aren't preserved byte-exact, which breaks signature verification downstream.

Here's the current landscape, honestly — including when to just stay with webhook.site.

1. CatchHook (this site)

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

• 1,000 requests per bin, 30-day retention with a free account (anonymous: 24 h). No paid tier exists.
• Replay is free — re-send any capture to your real endpoint byte-exact, or copy it as curl / fetch / Python / HTTPie.
• Custom URLs free (/h/my-stripe-dev).
• HMAC signature badges (GitHub, Stripe, Shopify, generic): paste the secret, every capture gets a ✓/✗ before you've written verification code.
• CLI free — live tail in your terminal, plus a relay mode that re-delivers webhooks to localhost without a tunnel; signatures still verify because bodies are byte-identical.
• Binary bodies byte-exact (hex view, raw download), configurable responses with templates like {{body.challenge}} (passes Slack/Zoom URL verification), request diff, JSON + HAR export, read-only share links per capture.

Trade-offs, honestly: live view is polling-based (~2 s, not instant-streamed WebSockets), there's no email-address capture (webhook.site can give you an inbox address too), and it's hosted-only. Full side-by-side: CatchHook vs webhook.site.

2. Beeceptor

Strong if what you really want is API mocking — rules, routed paths, templated responses. For pure inspection the free tier is about 50 requests per endpoint per day with short history. More detail here.

3. Pipedream (requestbin.com)

The old RequestBin domain now redirects to Pipedream. You get request inspection, but only inside their workflow-automation platform and behind a signup — an on-ramp to a paid product rather than a standalone bin. Fine if you're already building on Pipedream. The RequestBin story.

4. typedwebhook.tools

A minimal free inspector. Genuinely no-friction, but it's intentionally bare: short-lived URLs and inspection only — no replay, response control, signature checks, or exports. Good for a 30-second look.

5. Self-hosting

If payloads can't leave your network, self-host: the archived RequestBin fork, or a small handler you write yourself. You now maintain a service in order to debug a service, but for regulated environments it's the right call — none of the hosted options (including CatchHook) should get production PII.

When to just stay with webhook.site

If you're doing a one-off look at fewer than ~100 requests, never need replay or a custom URL, and the default expiry doesn't bite — it's mature, fast, and fine. The alternatives exist for the day your debugging session outgrows the free tier mid-incident.

Quick chooser

• Generous free limits + replay + CLI + signature checks → CatchHook.
• Mock API with routing rules → Beeceptor (or self-hosted Mockoon).
• Already on Pipedream → their built-in inspector.
• Payloads must stay in-house → self-host.

← All guides · Docs · CatchHook vs webhook.site