Webhook.site, but with replay + forwarding + half the price.
RequestBin captures every HTTP request the same way — full headers, body, query — and then lets you replay it into your local handler, auto-forward to production, or save it as a reusable mock. PRO at $12/mo (vs Webhook.site at $24/mo).
Why developers move off webhook.site
Real replay, not just inspection
Webhook.site shows you the request. RequestBin lets you replay it into your local server with one click — or edit headers/body first and re-send.
Forwarding rules built-in
Set up rules so captured webhooks auto-forward to Slack, your staging, or another endpoint. No XHR-polling-script workarounds.
Mock APIs, not just inboxes
Need to return a canned response to a Stripe webhook handler? RequestBin's mock side does that. Webhook.site only inspects incoming.
Webhook.site vs RequestBin
Both work great for the basic see-what-came-in use case. The gap widens when you need anything beyond inspection.
| Capability | Webhook.site | RequestBin |
|---|---|---|
| Public webhook URL | ✓ | |
| Real-time inspection | ✓ | |
| Replay into local code | ||
| Edit + re-send (modify before replay) | ||
| Forwarding rules | ||
| Mock APIs (canned responses) | ||
| Bulk NDJSON export | paid | |
| API access | paid | ✓ free |
| MCP server (AI IDE) | ||
| Free tier | 1 URL | 3 bins · 500 req/day |
| Starting price | $24 / mo | $12 / mo |
Already on Webhook.site? Switching takes 30 seconds.
You're not locked in. Webhook.site URLs are just paste-targets — change the URL in your provider's webhook config, and you're done.
- 1.Sign up at RequestBin (free, no credit card).
- 2.Create a bin → copy its URL.
- 3.Paste it into Stripe/GitHub/wherever your webhook is configured.
- 4.Old Webhook.site URL stays around until you delete it. No data lost, no rollback risk.
Try the parts Webhook.site doesn't have.
Replay, forwarding, mock APIs, MCP — all on the free plan. Upgrade only if you need higher volume or longer retention.
Other integrations
Other integrations under /apps.