improved

Webhook delivery updates

A Fail-Fast Policy Update: Accelerated Webhook Timeout

The initial webhook timeouts will change from 10 seconds to 0.5 seconds, and retries will still
have a 10-second timeout. If a webhook fails on the first attempt due to a response taking too long, it will still be retried as explained in our Failure and Retry Policy.

The webhook timeouts evolution will affect you if:

  • If your webhook endpoints take over 0.5 seconds to respond.
  • If you don't verify webhook uniqueness upon receipt.

If either applies to you, we recommend adjusting your webhook setup.

When your initial webhook response takes more than 0.5 seconds, it might trigger a retry, even if it is processed correctly on your side, potentially leading to duplicates. To prevent this:

  • Send the response status as soon as possible.
  • Save the event_id attribute available in payload to ensure its uniqueness.

Take a moment to review our dedicated guide to better understand these changes.

🚧

Warning

These changes are effective since 18/10/2023.