Skip to main content
Every chat agent can POST its own conversation events to a URL you control — separate from the account-level webhook in Settings. Both can be active at once, each with its own event list.

​
Settings

​
Events

A chat agent’s webhook covers conversations only. call_ended is not offered here — it comes from the call pipeline, which knows the voice agent that ran the call.
message_status_updated is high volume — every outbound message reports two or three times. Subscribe to it only if you are actually processing delivery state, and make sure your endpoint can absorb the rate.
Setting a URL with no events selected sends nothing. The builder warns you when that happens.

​
Headers

Each header row is a key plus a value from one of two sources:
Never paste a token, API key or signing secret in as a custom value. Save it in the Secrets Vault and reference it — vault values are stored encrypted, custom values are stored as typed.

Webhook reference

Payload shapes and delivery semantics

Secrets

Where credentials belong