Delivery Behaviors

Understand how [e-mail] delivers events to your webhook endpoint.

This section helps you understand the behaviors to expect regarding how [e-mail] sends events to your webhook endpoint.

Retry Behavior

[e-mail] attempts to deliver a given event to your webhook endpoint for up to 3 days with an exponential backoff.

If your endpoint is disabled or deleted when [e-mail] attempts a retry, future retries of that event are prevented. However, if you disable and then re-enable a webhook endpoint before [e-mail] can retry, you can still expect to see future retry attempts.

Disable Behavior

[e-mail] attempts to notify you of a misconfigured endpoint by email if the endpoint hasn’t responded with a 2xx HTTP status code for multiple days in a row. The email also states when the endpoint will be automatically disabled.

Event Ordering

While events are usually delivered in order, your integration should not depend on it. BrandApi doesn’t guarantee delivery of events in the exact order in which they’re generated.

For example, re-indexing a brand might generate both brand.company.updated and brand.updated events. Your endpoint shouldn’t expect delivery of these events in a specific sequence and needs to handle them accordingly. You can always use our API to fetch the most current state of an object if you receive an update event out of order.