Guide

Deduplication Patterns

Webhook systems should expect duplicates. Providers retry, networks fail, and manual replay can intentionally send the same business event again.

Good deduplication combines receiver idempotency with routing rules that reduce obvious duplicate traffic.

Where To Deduplicate

  • At the receiver, store provider event ids before side effects.
  • In FastHook, use deduplication rules for repeated event envelopes within a time window.
  • During replay, keep business operations idempotent so recovery is safe.

Keys To Use

  • Provider event id when available.
  • FastHook event id for delivery-level tracking.
  • A business id plus event type when provider ids are missing.

Next