Send an application message or receive a channel event
For application messaging use channel=api in the query and a ChannelApiToken from a deployed Channels API client. The body channel is a customer channel allowed for that client, such as email. Supply a unique id per message; retry the identical payload with the same id. A reused id with changed input or pending previous delivery returns 409. Omit conversationId to start a new conversation; include the returned ID to continue, keeping the same customerId and channel. Replies are asynchronous and arrive at the configured signed webhook. The JSON example documents API messaging; other transports use adapter-specific payloads.
Authentication
Token for one deployed API client, configured in Project → Channels.
Short-lived widget session capability
Query parameters
Ingress transport. Use api for application integrations. Other public transports are widget and twilio; their payloads and credentials differ.
Workspace identifier; required for API clients.
Request
The JSON schema below describes channel=api. Widget sessions use their own JSON envelope; Twilio uses application/x-www-form-urlencoded. Internal AI callbacks are configured by LogicDialog.
Response
Twilio SMS durably queued; empty TwiML acknowledgement.