Replay failed webhooks

Missed or failed deliveries are the usual reason developers lose hours. ReplayHooks stores the original request so you can fire it again.

How replay works

Select an event in the inspector.
Open the Replay tab (or press r).
Choose the endpoint's default forward URL or paste an ad-hoc target.
Toggle preserve original headers when your handler needs signatures.
Review status, latency, and response body preview.

# Original capture (already stored)
curl -X POST https://hook.replayhooks.com/x/<your-token> \
  -H 'Content-Type: application/json' \
  -d '{"id":"evt_failed","type":"invoice.payment_failed"}'

◈ replay result

Target

https://httpbin.org/post

200 OK · 42ms

{ "received": true }

replay result card with 200 OK

Localhost targets

Your laptop is not reachable from ReplayHooks cloud infrastructure. Replay to a public staging URL today. Localhost replay requires the upcoming CLI tunnel; add your email in the replay dialog waitlist so we can prioritize it.

Tips

Replay history is stored per event so you can compare attempts.
Over-quota free events stay captured; upgrade to unlock blurred payloads, then replay.