POST 1 credit

Request Replay

Replay a captured request to a specified target URL

How to Use

  1. 1. Identify the `bin_id` and `request_id` of the captured request you want to replay.
  2. 2. Send a POST request with the `target_url` where you want the request forwarded.
  3. 3. The API replays the original request (same method, headers, and body) to your target URL.
  4. 4. Inspect the `response_status`, `response_headers`, and `response_body` fields to verify how the target handled the request.

About this Tool

Request Replay takes a previously captured HTTP request from a bin and forwards it to a new target URL. The original method, headers, and body are preserved, allowing you to re-test webhook payloads against your local development server, staging environment, or any other endpoint.

This is invaluable for debugging webhook integrations — capture a real payload once, then replay it repeatedly while fixing your handler code. Authentication and hop-by-hop headers are stripped automatically for safety.

The response includes the target server's status code, headers, and body so you can verify the result without leaving the API.

Use Cases

Webhook handler debugging

Replay a real payment or event callback against your local server

Staging environment testing

Forward production webhook payloads to staging for verification

Error reproduction

Replay a request that caused an error to reproduce and fix the issue

Load testing

Replay the same request multiple times to test handler performance

FAQ

Which headers are included in the replay? expand_more
All original request headers are forwarded except hop-by-hop headers (Host, Connection, Keep-Alive, Transfer-Encoding) and authentication headers (x-api-key, x-rapidapi-key) which are stripped for security.
Is there a timeout for the replay request? expand_more
Yes, replay requests have a server-configured timeout. If the target server doesn't respond in time, you'll receive a 504 Gateway Timeout error.
Can I replay to localhost or internal IPs? expand_more
No, the replay endpoint includes SSRF protection that blocks requests to private IP ranges, localhost, and internal network addresses. The target must be a publicly accessible URL.
Try Request Replay →