What a webhook forwarder is
A webhook forwarder is a public URL on yourdevtools.pro that, when hit by an external service (Stripe, GitHub, Linear, your own integration), immediately proxies the request to your real target URL and shows you the outcome. Unlike a simple receiver, this tool does not absorb traffic - it acts as a transparent reverse proxy.
You paste our URL into the Stripe dashboard and every event still reaches your production endpoint, while you simultaneously see each delivery in the panel with its status code, duration, and full body.
How to use it
- Enter a target URL: full `https://your-domain/webhooks/stripe`. Must be public https or http - localhost and private IPs are blocked.
- Click "Generate" - you get a unique forwarder URL like `yourdevtools.pro/api/forward/abc12345`.
- Paste that URL into the external service's settings (Stripe Webhooks, GitHub Webhooks, your own config).
- Trigger an event (e.g. "Send test event" in Stripe). Your server receives the request directly from us, with original headers and body.
- In the panel you see every request: method, status code your server returned, duration, headers, body. Click a row to expand.
- Change the target without minting a new id: edit the "Target" field → "Update target". Stripe never notices.
- A forwarder expires after 24 hours of inactivity. An open tab resets the timer on every poll.
When this is useful
Six typical production-grade forwarder scenarios:
- Production webhook endpoint where you want full visibility during the first days post-launch, when every event matters.
- Staging / preview environments where you want to route webhooks without reconfiguring the external service each time (you change the target, the URL stays).
- Debugging 500s on production: your endpoint returns an error but logs are sparse. The forwarder shows the exact request that caused it plus the first 4 KB of your response.
- Migrating webhooks to a new domain: temporarily point external services at the forwarder, it forwards to the new infrastructure, you keep a full audit log.
- Sharing an integration across a team: one person sets up the forwarder, the whole team sees the same requests prod is seeing for 24h.
- Testing rate limits and timeouts: the forwarder enforces an 8-second timeout, so you can see in the panel which requests timed out on your side.
Related tools: webhook receiver (inspect only, no forwarding), HTTP request tester, cURL converter.
Questions and answers
A receiver just stores the request and replies 200, it never forwards anywhere. A forwarder proxies the request to your target URL, waits for your server's response (up to 8 s), returns that status code to the sender (e.g. Stripe), and keeps a full log of both sides. It is the production-grade variant: use it when you need a stable URL plus visibility, not just debug-only inspection.