Webhook Guides

Webhook Replay Systems

A webhook replay system lets teams recover after missed delivery, bad destination code, credential failures, routing mistakes, and temporary outages. The hard part is not sending the HTTP request again. The hard part is replaying the right events without creating duplicate side effects or overloading the receiver.

FastHook keeps the original request, routed event, destination attempts, and retry history together so replay can be a controlled recovery action rather than a manual copy-paste from logs.

Webhook replay decision map for request replay, event retry, and bulk recovery.
Choose the smallest replay path that fixes the incident. Request replay and event retry have different blast radiuses.

Replay models

ModelWhat runs againUse when
Request replayOriginal request through current routing rules.Routing, filtering, or transformation changed.
Event retryOne destination event delivery.Destination failed after routing succeeded.
Bulk replayA filtered window of stored requests or events.Outage recovery after one-event retry succeeds.

Replay safety requirements

  • Preserve raw payloads and headers before processing.
  • Make destination receivers idempotent before retrying events.
  • Filter by provider, destination, status, and time window before bulk replay.
  • Retry one event and inspect the new attempt before replaying many events.
  • Throttle replay into fragile or rate-limited destinations.

Retry one failed event

Retry event
curl -X POST "https://api.fasthook.io/v1/events/evt_01JYFAILED/retry" \
  -H "Authorization: Bearer fhp_xxx" \
  -H "x-team-id: tm_3b5335b627084a838b"

Related guides