Reply to a conversation
Send a text or email reply to the customer on an existing conversation, the same as clicking Send in the dashboard. The customer receives it. A call with a phone number can get a text even when text is not in its channels. Otherwise reply only on a channel in the conversation’s channels. Website chats with neither text nor email in channels, and calls with no phone number and no email thread, cannot get a reply. The key’s creator must be allowed to message the customer in the dashboard. A customer who opted out by replying STOP gets no texts, but email still sends. The reply goes only to the conversation’s customer. The reply shows in the thread and Activity under the key’s creator. A failed send still returns 201 with delivery_status failed. Requests from this playground go to production and message a real customer. Customer API.
Headers
Body
Scoped to the API key's creator and one conversation. A retry with the same idempotency key on the same conversation, from any API key that person created, returns the first message and sends nothing. Reusing the key with a different body or channel returns 409.
^[A-Za-z0-9._:-]{1,120}$Response
The reply was accepted. Check delivery_status to see whether it went out. A retry with the same idempotency key returns the first message.
queued means the carrier accepted the reply and has not sent it yet. failed means the send failed and error says why. unknown means the provider did not answer, so check the conversation later.
queued, sent, delivered, failed, unknown "queued"