Skip to main content

Considerations and limitations

When integrating with our webhooks, it's important to be aware of certain considerations and limitations to ensure a smooth and efficient implementation. This page outlines key points you need to know.

Endpoint Registration Limits​

  • Maximum Endpoints: You are allowed to register up to 2 webhook endpoints per account.
  • Additional Endpoints: If you require more than 2 endpoints, please contact our sales team to discuss your needs.

Event Ordering and Concurrency​

  • It is important to note that webhook events are not guaranteed to be processed in order.
  • Due to the concurrent nature of webhook delivery, events may arrive out of sequence.

This can lead to inconsistencies and potential race conditions. Users should be aware of these limitations and design their systems to handle possible unordered events processing, by applying proper validations with the eventDate property.

Event Delivery​

  • Batching Events: Our platform can send up to 100 events per request. This batching mechanism helps minimize the number of requests sent to your server and avoids spamming your API with too many individual requests.
  • Timing: If there are no events received within a lapse of 5 seconds, we will send the request with the events accumulated so far.

Retry Mechanism​

  • No Retries: Our platform does not provide retry operations for failed webhook deliveries at this moment.
  • Ensure Throughput: Make sure your API can handle the request throughput and is capable of processing the events efficiently.
  • Response Status: Ensure your webhook endpoint returns a 202 Accepted HTTP status code to acknowledge successful receipt of the request.

Handling High Throughput​

To handle the potential high throughput of events:

  • Scalability: Ensure your server infrastructure can scale to handle bursts of incoming webhook requests.
  • Asynchronous Processing: Implement asynchronous processing to quickly acknowledge the receipt of the webhook and process the events in the background, our platform only waits 5 seconds before killing the request.