Resolve a Chat and send a Message
Resolve or create a Chat, then send a Message.
Blocking is silent on this path. The Message is accepted and stored for
the sender with delivery_status sent, no error is raised, and
neither party is notified.
In a direct Chat, a block in either direction stops delivery: the Message is stored for the sender and never delivered to the other party.
In a group Chat, blocking is one way. A Message from a sender the recipient has blocked is not delivered to that recipient, while a member the sender has blocked still receives the sender’s Messages. Every other member receives the Message as normal.
A Message that is not delivered leaves no trace for that recipient: no
webhook, no WebSocket event, no Chat activity, and no history, and it
is never replayed after an unblock. The sender’s message.delivered
fires when at least one recipient was delivered.
Authorizations
Bearer token authentication. Include your API token in the Authorization header.
Format: Authorization: Bearer <your-token>
Headers
Optional idempotency key for the send. Reuse the same key to safely
retry without sending twice. May also be supplied as
message.idempotency_key.
255Body
Response
Message accepted for delivery
The resolved Chat and resulting Message.
The reused or newly created Chat.
Handle of the authenticated sending Contact.
Whether the resolved chat is a group chat.
Contacts in the resolved Chat.
The primary message that was sent.

