Webhook event reference - Sendora

Webhooks are at-least-once notifications. Your consumer must authenticate, acknowledge quickly, and deduplicate by event ID before applying business changes.

Common envelope

{
  "id": "evt_01J...",
  "event": "reply.received",
  "timestamp": "2026-09-20T10:05:32Z",
  "data": {}
}

Treat id, event, and timestamp as envelope metadata. The data shape is event-specific and must be validated against the event documented for your integration.

Consumer flow

receive → read raw body → verify signature → deduplicate event ID → enqueue → return 2xx

Do not parse and mutate business state before signature verification. Do not perform long-running work before acknowledging the delivery.

Delivery behavior

Non-2xx responses and timeouts can be retried. A duplicate delivery is not necessarily a duplicate event. Persist the event ID and handler result so retries are safe. See Webhooks for endpoint registration, secret rotation, test deliveries, and the current event catalog.