One workspace for every webhook you're actually debugging, not just one you caught once.
Stripe payments, Twilio SMS, GitHub deploys, your own internal callbacks — real integration work means juggling several webhook sources at once, over days or weeks, not a single disposable capture URL. RequestBin keeps a bin per source, none of them expire, and every captured request can be replayed (edited or as-is) whenever you need to re-check a fix.
Why "workspace" instead of "inspector"
One bin per source, organized
A separate bin for Stripe, Twilio, and your own callbacks — not one shared inbox where everything blurs together. FREE gives you 3; PRO gives you 20.
Bins don't expire
Debugging a webhook integration is rarely a one-sitting job. Come back tomorrow, next week — the bin, its URL, and its captured history are still there.
Replay to re-check a fix
Shipped a fix for a webhook handler bug? Replay the exact request that broke it — as-is, or edited — instead of waiting for the real event to fire again.
What's actually in it
- Full request capture — headers, body, query — for every webhook that hits a bin.
- Replay any captured request into your local dev server or a production endpoint, unedited or modified first.
- Forwarding rules so a captured webhook can auto-relay to Slack, staging, or wherever the team needs eyes on it.
- Free API keys + an MCP server, so an AI coding agent (Claude Code, Cursor) can drive the same workspace without a browser tab.
- A mock-API side too, for the outbound half of integration testing — canned responses when you need to simulate the OTHER service's webhook back to your code.
Set it up once, keep debugging as long as you need to.
3 bins, 500 requests/day each, free. Upgrade to PRO ($12/mo) for 20 bins, unlimited requests, and full replay/forwarding.
Other integrations
Other integrations under /apps.