Skip to navigation

Reply webhooks and events

What clients can subscribe to today

An API client’s configured reply webhook receives message.created when an assistant or human reply is approved for customer delivery. The event includes the text, so you can deliver it immediately, then fetch history if needed.

There is currently no general client event subscription API for call completion, tool execution, state changes, draft creation, read receipts, or “reply is being prepared”. Internal drafts are not customer messages and are not emitted. If you require additional event types, they need a separate implementation rather than a documentation setting.

When Review every reply is enabled in Channels, a reply can remain held until a staff member sends it in Live Chat. HTTP 202 does not promise an immediate webhook.

Verify and acknowledge

The request includes LogicDialog-Signature: t=UNIX_SECONDS,v1=HEX_HMAC_SHA256 and Idempotency-Key. Compute HMAC-SHA256 over the timestamp, a literal full stop, and the exact raw HTTP body, using the client’s outbound signing secret. Reject stale timestamps (for example, outside five minutes), and compare decoded signatures in constant time. Parsing and re-serialising JSON before verification changes the signed bytes.

Persist the event and return 2xx promptly. The same event ID is reused for retries: deduplicate on id or Idempotency-Key. Delivery is at least once. Webhook URLs must be public HTTPS, redirects are not followed, and requests time out after 15 seconds.

LogicDialog manages durable delivery and retries. Failed deliveries normally retry around every 30 seconds; contact your administrator if delivery processing is unavailable. Archival failure after a successful webhook does not cause the customer webhook to be resent.

Fetch history after notification

Use the event’s conversationId with the client history endpoint and the same API token/client identifiers used to create the conversation. History contains public messages, status and an available summary. It can briefly lag the webhook while provider archival finishes; retain the webhook payload and retry history retrieval when appropriate.

Operator events are separate

Operator events is a server-sent event stream for signed-in operators with conversations.review. It emits ready and changed (containing an internal record ID), prompting the staff UI to reload. It is not available using a channel API key and is not a substitute for a client webhook subscription.