Skip to main content
GET
This endpoint returns a cursor-paginated list of conversations belonging to the authenticated user’s assistants. Use this to display conversation history, filter by type, or integrate with your CRM.
This endpoint uses cursor-based pagination for better performance with large datasets. Use next_cursor and prev_cursor to navigate between pages.

Query Parameters

type
string
Filter conversations by type. Possible values: test, widget, whatsapp, api
assistant_id
integer
Filter conversations by assistant ID (must belong to the authenticated user)
customer_phone
string
Filter conversations by customer phone number (exact match). Useful for finding all conversations with a specific customer.
whatsapp_sender_phone
string
Filter conversations by WhatsApp sender phone number (exact match). Useful for finding all conversations from a specific WhatsApp business number.
external_identifier
string
Filter conversations by external identifier. Useful for finding conversations linked to your external system records.
per_page
integer
Number of conversations per page (1-100, default: 15)
cursor
string
Cursor for pagination. Use next_cursor or prev_cursor from a previous response.

Response Fields

data
array
next_cursor
string
Cursor to fetch the next page of results. Pass this as the cursor parameter in your next request. null if there are no more results.
prev_cursor
string
Cursor to fetch the previous page of results. null if this is the first page.
per_page
integer
Number of items per page

Conversation Types

Filter Parameters

All filter parameters use indexed columns for efficient querying:

WhatsApp Conversation Details

For WhatsApp conversations, the response includes additional fields:
  • whatsapp_sender: The business WhatsApp number that handled the conversation (your WhatsApp sender’s name and phone)
  • customer: The customer who initiated or received the conversation (their name and phone number)
These fields are only present for whatsapp type conversations and help you identify the parties involved when integrating with your CRM or support systems.

API Conversation Details

For API-created conversations, you can set an external_identifier when creating the conversation. This identifier is returned in the response and can be used to:
  • Link conversations to your CRM leads or contacts
  • Track conversations across your internal systems
  • Filter conversations by your external reference

Use Cases

  • Analytics Dashboard: Display conversation metrics and trends
  • CRM Integration: Sync conversation data with your customer database using external_identifier
  • Customer Lookup: Find all conversations with a specific customer using customer_phone
  • Quality Monitoring: Review conversation volumes by type and assistant
  • Billing Review: Track conversation costs across your organization