Request Replay
Replay lets you re-send any captured webhook request to a URL of your choice. Perfect for debugging integrations without waiting for the real event to fire again.
What is Replay?
When you capture a request in a bin, you can replay it to any destination URL. RequestBin sends the exact same HTTP method, headers, and body to the target. This is a PRO feature.
Replay from Bin Detail
- Open a bin and select a captured request
- Click the Replay button in the interaction detail panel
- Enter the destination URL (e.g., your local server)
- Optionally modify headers or body before sending
- Click Send and view the response
Replay from HTTP Requester
You can also open any captured request in the HTTP Requester tool. This gives you full control over method, URL, headers, and body with a code editor. The HTTP Requester also generates cURL, Python, and Node.js code for your request.
Replay Statuses
- Pending — the replay job is queued and waiting to be sent
- Success — the target server responded with a 2xx status code
- Failed — the target server responded with a non-2xx status or the connection timed out
- Blocked — the destination was blocked by SSRF protection (see below)
SSRF Protection
For security, RequestBin blocks replay requests to private/internal IP ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, etc.). This prevents server-side request forgery (SSRF) attacks. If you need to test against localhost, use a tunneling tool like ngrok or cloudflared.
Troubleshooting
- Connection timeout— make sure your target server is running and reachable from the internet
- SSL errors— ensure your target has a valid SSL certificate if using HTTPS
- Blocked destination— private IPs are not allowed; use a public URL or tunnel
- Large payloads— replay body size is limited to 1 MB