Send Message (Async)
Accepts an inbound customer message and answers immediately without waiting for the agent’s reply. Every reply — and the turn’s completion — is delivered to the agent’s delivery URL instead of riding back on this response.
Requires the agent to have a delivery URL configured; use this endpoint when your integration can’t hold a request open for the length of a turn (e.g. a webhook-based gateway with its own timeout). Otherwise, Send Message is simpler.
Takes the same parameters as Send Message, including idempotency_key, interactive-message fields, and supported_interactions.
Authorizations
Body
Your identifier for this exact turn. Strongly recommended on this endpoint: since the reply arrives later on the delivery webhook, this is what lets you correlate it back to the request that triggered it (it's echoed on every delivered envelope). A retry with the same key returns the original 202 instead of accepting the turn twice. Can also be sent as an Idempotency-Key header instead of a body field.
"wh-2f8a1c-attempt-1"
Optional. Which of your own channels the message came in on. Without session_id, the message goes to the customer's active session on this channel (a new one is created if there is none). With session_id, it must be that session's channel or the request fails with 422 channel_mismatch. Omit it to use the session with no channel, as before.
whatsapp, instagram, web, app "whatsapp"
message for a normal text message (default). interaction_response to answer an interactive message the agent sent — see Interactive messages.
message, interaction_response "message"
Structured answer to a pending interactive message. Send this or option_id, never both. See Interactive messages.
Declares which interactive message types your client can render. See Interactive messages.
Response
Turn accepted. The reply (and every other reply this turn produces) is delivered to the chat delivery webhook, not in this response.
