Webhook Delivery and Sequencing

Due to the distributed nature of Send’s platform, we cannot guarantee that every intermediate status transition for an object will be delivered via webhook. While we aim to provide comprehensive status updates, there are specific considerations to keep in mind:

• First and Last Events: Send ensures that the first and last status change events for each object are always delivered reliably.
• Intermediate States: In cases where objects transition through processing states rapidly, intermediate status events may occasionally be skipped. This is an expected behaviour to ensure efficiency and system performance.
• Even Sequencing: Please be aware that webhooks can sometimes arrive out of order. Take note of the createdAt timestamp in webhooks to ensure you process them in the correct order.

Recommendations for Developers

To handle potential gaps in intermediate status events:

1. Design your system to rely on the guaranteed delivery of the first and last status events for critical workflows.
2. Implement mechanisms to query the latest status of an object using the appropriate API endpoints if intermediate states are essential for your application.
3. Use webhooks in conjunction with periodic reconciliation processes to ensure data consistency.