Skip to main content
Understand how Brand API delivers webhook events to your webhook endpoint. This section explains the expected delivery behavior, retry logic, endpoint disabling rules, and event ordering considerations when Brand API sends webhook events to your application.

​
Retry Behavior

Brand API attempts to deliver each webhook event to your endpoint for up to 3 days using exponential backoff. If your webhook endpoint is disabled or deleted while Brand API is retrying an event, future retry attempts for that event will stop. If you disable and then re-enable a webhook endpoint before the next retry attempt, Brand API may continue sending retry attempts for that event.
Make sure your webhook endpoint is always available and returns a successful 2xx HTTP status code after receiving an event.

​
Disable Behavior

Brand API may notify you by email if your webhook endpoint appears to be misconfigured or unavailable. If your endpoint does not respond with a 2xx HTTP status code for multiple days in a row, Brand API will send an email warning. The email will also include information about when the endpoint may be automatically disabled.
Monitor webhook failures in your backend logs so you can fix endpoint issues before automatic disabling occurs.

​
Event Ordering

Webhook events are usually delivered in order, but your integration should not depend on exact ordering. Brand API does not guarantee that events will arrive in the same order they were generated. For example, re-indexing a brand may generate both: 
brand.company.updated
brand.updated