Ways to replay
| You want to | Use |
|---|---|
| Send it to your app on your machine, unchanged | Send to my tunnel on the event, or whq replay <id> 3000 |
| Change it first, then send it anywhere | Edit and send on the event |
| Try a failed delivery to a destination once more | Send again on that delivery |
| Let your coding agent do it | The MCP server's replay_webhook, after you confirm |
Replays work on every plan and don't count towards your plan's events. Edit and send and Send again need editor access to the endpoint's workspace.
Replay to your machine
Start a tunnel for the endpoint:
whq listen 3000 --endpoint acme-stripe-test
While it runs, every event on that endpoint has a Send to my tunnel button. It sends the webhook to your app unchanged, with its original method, path, headers and body, and the page says which machine it went to. If no tunnel of yours is listening, the page asks you to run whq listen first.
From the terminal you don't need a tunnel at all. Pass the event's short id (shown in the dashboard and by whq listen) and where to send it:
whq replay 3f9a2c1 3000
whq replay 3f9a2c1 https://app.acme.test:3000/webhooks
Example: your handler crashed on a charge.refunded event yesterday. You fix the bug, run whq replay 7c2e9a1 3000, and your app now returns 200 against the real payload. More options in the CLI reference.
Edit and send
Edit and send on an event opens a copy of the request you can change:
- Method, Path and Query. The path and query are added to the destination's or URL's own.
- Headers: add, change or remove any.
- Body: sent exactly as written. A binary body can't be edited and is sent unchanged.
Then pick where it goes under Send to:
- My tunnel: your machine, where
whq listenis running (shown only while it runs). - A destination: one of the endpoint's destinations, with the destination's own headers. One try, no retries.
- A URL: any public server, like
https://staging.acme.dev/webhooks. Private and local addresses are refused; for your own machine, use your tunnel.
Click Send. The captured event never changes.
Example: you suspect your handler breaks when amount is zero. Open a real charge.succeeded, change amount to 0, and send it to your tunnel. Your app returns 500, and you've found the bug without waiting for a real zero-amount charge.
Changing the body breaks the provider's signature, so your app's verification will reject it. To test a changed body with a valid signature, send a signed test event instead.
Retry a failed delivery
When a delivery to a destination has Failed after its automatic retries, or was cancelled, open the event and click Send again on it. It's sent once more, now, with no further automatic retries, and keeps the same Idempotency-Key.
It isn't sent when:
- the destination is paused: Resume it in the endpoint's settings first, and its waiting webhooks go out too (Forwarding),
- the delivery is Held over the monthly limit: an owner sends held deliveries from the Usage page (Plans and limits).
How replays show in deliveries
Every replay is recorded on the event, below its forwarding deliveries:
- Edited replay → Staging API (or the URL): expand it to see the Request as it was sent (method, URL, headers and body, with secrets masked) and the Response.
- Tunnel · MacBook: a replay or delivery to your machine, with what your app answered and how long it took.
- Send again adds an attempt to the same delivery's list of attempts.
Replays to a URL, a tunnel or with Edit and send are tried once. If they fail, replay again. Each edited replay is a new delivery with its own Idempotency-Key, so your server treats it as a new request.