Conversations

Threads in the shared inbox, assignment and AI handover.

The conversation object

As returned by GET /conversations, one element of the list. Every endpoint below that returns this resource returns exactly these fields.

Name	Type	Description
`id`required	`string (uuid)`	UUID
`contact_id`required	`string (uuid)`	UUID
`contact`required	`object`	The person on the other side
`contact.id`required	`string (uuid)`	UUID
`contact.name`required	`string \| null`	Display name
`contact.phone`required	`string \| null`	E.164 phone number, when the channel has one
`channel`required	`string (enum)`	The channel the thread lives on`whatsappmessengerinstagramwebchatpersonal_whatsapp`
`connection_id`required	`string (uuid) \| null`	For personal WhatsApp: the linked number this thread is on
`status`required	`string (enum)`	Where the thread sits in the inbox`openpendingclosed`
`assigned_to`required	`string (uuid) \| null`	Member user id, or null when unassigned
`ai_ownership`required	`string (enum) \| null`	Who is answering: the assistant, a human, or null = inherit from the channel’s assistant binding`aihuman`
`needs_attention`required	`boolean`	The assistant handed this thread to a human and nobody has picked it up
`handoff_reason`required	`string \| null`	Why the thread was handed to a human, when it was
`last_message_text`required	`string \| null`	Preview of the most recent message
`last_message_at`required	`string (date-time) \| null`
`unread_count`required	`integer`	Inbound messages not yet marked read
`created_at`required	`string (date-time)`	ISO 8601 timestamp
`updated_at`required	`string (date-time)`	ISO 8601 timestamp

8 endpoints, each on its own page with its parameters, responses, error codes and samples in curl, Node and Python.