List conversations
GET /api/conversations
Returns a paginated list of conversations, optionally filtered by workspace, status, or text search. Results are ordered by the most recent activity (lastMessageAt). Use the offset and limit parameters to paginate through large result sets.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Filter conversations to a specific workspace.
Filter by conversation status. Accepted values: ‘new’, ‘active’, ‘human_managed’, ‘resolved’, ‘waiting’.
Maximum number of conversations to return per page. Defaults to 50.
Number of conversations to skip before returning results. Defaults to 0.
Responses
Section titled “ Responses ”A paginated list of conversations with the total count of matching results.
Paginated list of conversations. Use the total field to determine how many conversations match your filters, and offset/limit query parameters to page through results.
object
The conversations on the current page.
A conversation represents a threaded exchange between a customer and your organization on a specific channel. Conversations are created automatically when a new inbound message arrives, or manually via the compose endpoint. Each conversation tracks its lifecycle through status transitions and maintains links to the associated contact and account.
object
Unique identifier for the conversation.
Example
c1a2b3c4-5678-9abc-def0-1234567890abThe tenant this conversation belongs to.
Example
a0b1c2d3-4567-89ab-cdef-0123456789abThe workspace this conversation is assigned to.
Example
w1a2b3c4-5678-9abc-def0-1234567890abThe channel (email, WhatsApp, chat widget, etc.) through which this conversation is conducted.
Example
ch1a2b3c-5678-9abc-def0-1234567890abThe contact (individual person) participating in this conversation. May be null if the contact has not yet been resolved.
Example
ct1a2b3c-5678-9abc-def0-1234567890abThe account (company or organization) the contact belongs to. May be null for B2C conversations or if the account has not yet been resolved.
Example
ac1a2b3c-5678-9abc-def0-1234567890abCurrent lifecycle status of the conversation. Possible values: ‘new’ (just created, no AI response yet), ‘active’ (AI is managing), ‘human_managed’ (a human agent has taken over), ‘resolved’ (closed with an outcome), ‘waiting’ (awaiting customer response).
Example
activeAI-generated summary of the conversation, updated after each turn. Provides a concise overview of the discussion so far.
Example
Customer asked about delivery times for order #4521. Agent confirmed 3-5 business days to Germany.Subject line of the conversation. For email conversations, this is the email subject. For other channels, it may be AI-generated or null.
Example
Re: Delivery time for order #4521A short description of how the conversation was resolved. Set when the conversation is moved to ‘resolved’ status, either by the AI or a human agent.
Example
Delivery timeline confirmed, customer satisfied.Total number of messages in the conversation thread, including both customer and agent messages.
Example
6Timestamp of the most recent message in the conversation. Null if no messages have been exchanged yet.
Example
2026-03-25T11:42:00.000ZTimestamp when the conversation was created.
Example
2026-03-24T08:15:00.000ZTimestamp when the conversation was last updated (status change, new message, etc.).
Example
2026-03-25T11:42:00.000ZTotal number of conversations matching the applied filters, across all pages.
Example
142