List customer conversations
Return matching records as data[], with pagination.has_more and pagination.next_cursor. Each item uses the same native payload as single-record retrieval. Required start_time/end_time are epoch seconds with an inclusive start and exclusive end, spanning at most 31 days. limit is 1–50 (default 20); sort_order is asc or desc (default desc). Optional filter applies the same standard field matching as the dashboard. The record follows the existing analytics webhook format: audio_to_text.transcript for calls or chat_transcription.transcript for chats, meta_analytics and native conversation_analytics modules. Customer analytics and customer timeline are excluded. For larger datasets, use Create export to obtain a CSV download link. Each export supports at most 31 days, 100,000 records and 200 MiB (209,715,200 bytes); split longer periods into adjacent windows.
Authentication
Path parameters
Identifier returned by the corresponding list operation. Nonempty, at most 255 characters; whitespace-only values and control characters are rejected.
Query parameters
Required authorized service. Client identity is derived from the API key. Nonempty, at most 255 characters; whitespace-only values and control characters are rejected.
Timestamp used for filtering and ordering. Only conversation_time is currently supported for this resource.
Inclusive start in Unix epoch seconds. Must precede end_time; maximum window is 31 days. Milliseconds are invalid.
Order by conversation_time, then ID in the same direction. asc returns oldest first; desc returns newest first. Keep the same sort_order when continuing with a cursor.
Maximum records per page. Accepts integers from 1 to 50; defaults to 20.
Opaque continuation token, 1–4,096 characters; expires after 15 minutes. Repeat the same filters and sort_order. Omit for the first page. Copy pagination.next_cursor from the previous response; see the pagination walkthrough for first and next-page requests.
Dashboard filters as one URL-encoded JSON object (maximum 16 KB). All conditions must match. See the schema for fields, operators, and value constraints.