Ryder provides webhook delivery on an at-least-once basis. While Ryder makes reasonable efforts to deliver each webhook event successfully, Ryder does not guarantee exactly-once delivery. As a result, the same webhook event may be delivered more than once.

Customers integrating with Ryder webhooks are responsible for implementing idempotent webhook processing within their integration. This ensures that duplicate deliveries of the same event do not result in unintended duplicate processing or downstream actions.

To support idempotent processing, each webhook payload includes a signature field that may be used by your integration as an idempotency key to identify previously processed events and safely handle duplicate deliveries.

See Webhooks for more details about our webhooks, including event payload examples.