Guide
Replay a captured request
Send a captured request to your app again after you fix a bug, without waiting for the sender to try again.
- Applies to
- Starter and higher for the webhook check; durable tunnels
- Time
- About 3 minutes
- What it changes
- Sends a copy of a captured request to your app.
- Last reviewed
- , by Product documentation
Before you begin
What to know before you start
- Replay sends a request again to your app. If the request creates or changes something, such as a payment or an order, replaying it can do that again.
- Replay is not available on a tunnel with a password, because InstaWormhole never holds the password. It is also not offered for WebSocket requests.
Steps
Step 1. Select the request and choose Replay.
A dialog shows the method, the path, the headers and, if it was kept, the body. You can edit them. A warning appears for methods that change data, such as POST.
You should see: The dialog shows what will be sent.
Step 2. Confirm the replay.
The request goes to the tunnel's public address and your app. It is marked with an X-Instawormhole-Replay header. You can replay once every 5 seconds, and each replay is recorded in the workspace audit log.
You should see: The dialog shows the result of the replay.
To check: The replayed request appears as a new row in the inspector.
You are done when
- The replayed request appears in the inspector and your app answered it.
If something goes wrong
- The Replay button is disabled.
- Replay is not offered on a password-protected tunnel. Use Copy as cURL and add the password yourself.
Undo or clean up
- None. A replay is a normal request and appears in the inspector like any other.
Good to know
To use a request somewhere else, choose Copy as cURL or Download HAR. Both are made in your browser from the stored request, so redacted values stay redacted, and a review step lists what was removed.
Related
This page is part of Inspect and replay. Still stuck? Contact support.