Per-session configuration
Each session has its own webhook configuration, with two delivery modes:single — one URL for all events
single — one URL for all events
All enabled events of the session are sent to the same URL.
Useful when a single endpoint handles all the processing.
per_event — one URL per event
per_event — one URL per event
Each event has its own
webhookUrl, so you can route different events
to different endpoints.Destination URL of the event (in
per_event mode) or inherited from the single
configuration (in single mode).Common envelope
Every webhook arrives with the same envelope. The event-specific content is indata.
Headers
This product does not send an HMAC signature with webhooks. To restrict the
origin, we recommend using a secret URL (with a token in the path) and/or validating the
User-Agent and the expected sessionId.Delivery and reliability
Retries (7 attempts, exponential backoff)
Retries (7 attempts, exponential backoff)
On failure, delivery is retried up to 7 times with exponential
backoff: approximately 5s, 10s, 20s, 40s, 80s and 160s between
attempts.
Permanent failures (404 / 410)
Permanent failures (404 / 410)
HTTP 404 or 410 responses are treated as a permanent failure:
delivery is no longer retried for that URL.
Timeout
Timeout
Each attempt has a 30-second timeout. Slow endpoints may be
considered a failure and be retried.
Circuit breaker
Circuit breaker
There is a per-URL circuit breaker: URLs that fail repeatedly are
temporarily paused to avoid overload.
Deduplication
Deduplication
Events go through Redis-based deduplication (5-minute TTL), reducing
duplicate deliveries of the same event within a short interval.
