Local Proxy
Forward requests from your public catcher URL to localhost via ngrok or any tunnel. Debug webhooks directly on your local machine.
Loading...This endpoint ID is shared with the Request Catcher. Requests sent to the URL above will be captured there and forwarded here.
Every request received at your catcher URL will be forwarded to the target below in real-time — headers, body, method, and path all preserved. Use a tunnel URL to reach your localhost, or any public HTTPS URL.
For localhost: paste the ngrok/tunnel public URL. For production: paste any HTTPS URL.
Our edge servers cannot reach your localhost. These free tools create a secure public tunnel to your local port. Run one, copy the public URL, and paste it in the Forward Target above.
brew install ngrok # or download from ngrok.comngrok http 3000A free ngrok account is required. Sign up at ngrok.com and run: ngrok config add-authtoken <token>
curl -X POST "" \
-H "Content-Type: application/json" \
-d '{"test":"forwarded"}'After sending, open the Request Catcher to see the captured request and its forward response.
Frequently Asked Questions
What is Local Proxy?
Local Proxy forwards every request received at your Request Catcher URL to a target URL you specify — such as your ngrok tunnel pointing to localhost. It acts like a transparent reverse proxy.
Why can't I just forward directly to localhost?
Our edge servers cannot reach your machine's localhost. You need a tunnel tool (ngrok, localtunnel, cloudflared) to create a public URL that routes to your local port.
Does it use the same endpoint as the Request Catcher?
Yes. Both tools share the same endpoint ID stored in your browser. Configure forwarding here, then visit the Request Catcher to watch requests arrive and see forward responses.
What happens if my local server is down?
The request is still captured by the Request Catcher. Forwarding will fail gracefully and log an error message visible in the Forward tab of each request.
Is there a request size or rate limit?
Forwarding has a 15-second timeout per request. Response bodies over 10KB are truncated in the display but the full request is always forwarded to your server.