Reliable webhooks with retries and deduplication
Verify incoming events, handle duplicates and out-of-order messages, and give people a way to recover failures.

In short
- Validate the signature against the original request body.
- Use the event ID for deduplication and track the object version you have applied.
- Retry temporary outages with increasing delays.
- Next steps
On this page
Verify the message before acknowledging it
Validate the signature against the original request body. Store the event durably before responding. Run business processing separately so a slow downstream call does not delay the acknowledgement.
Expect duplicates and ordering changes
Use the event ID for deduplication and track the object version you have applied. An update may arrive before a creation event. Provide a way to fetch the current state from the source. Replay should never send a second email or create another order.
Separate recoverable failures
Retry temporary outages with increasing delays. Move invalid events to a review list with the reason and reference. Test an expired signature, an out-of-order event and repeated delivery of the same message.
Next steps
Creagrid / actie
Practical checklist
Describe the problem and intended outcome.
Involve the people who use the process every day.
Test the riskiest assumption with a small prototype.
Define tests, ownership and maintenance up front.
