Delivery and retries

Sending Architecture

Your Server Response

To confirm receipt, your server must return any HTTP 2xx response.

HTTP 408, 425, 429, 5xx, timeout and retryable network failures use bounded full-jitter exponential backoff. Retry-After is honored within the configured cap. Other 4xx responses are permanent failures; the default retry budget is bounded by a three-day event age.

Delivery is at least once. Automatic and manual replay preserve event, event_version, event_id, timestamp and data, and begin a new attempt cycle. Consumers must deduplicate by event_id.