List conversations
Returns the organization's conversations, most recent message first.
Returns the organization's conversations, most recent message first.
The organization API key, sent as Authorization: Bearer <key>.
In: header
Query Parameters
How many items to return. Maximum 100.
1 <= value <= 10025How many items to skip from the beginning.
0 <= value01 <= length1 <= length1 <= lengthMatches against the contact name and the channel identifier.
1 <= lengthResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/conversations"{ "data": [ { "activityState": "string", "channel": "string", "contact": "string", "contactName": "string", "controlledBy": "string", "createdAt": "2019-08-24T14:15:22Z", "customerId": "string", "customerName": "string", "id": "string", "language": "string", "lastMessageAt": "2019-08-24T14:15:22Z" } ], "pagination": { "limit": 0, "offset": 0, "total": 0 }}Archive a customer DELETE
ARCHIVES the customer: they leave the active book and the listings, but their history is not destroyed. Deliberate — a buggy integration should not be able to wipe an agency's customer base.
Get the transcript of a conversation GET
Oldest first — the order of a transcript, so it reads the way it was spoken. Takes `limit` but no `offset`, and that is deliberate rather than an omission: messages live in two different stores depending on how the channel arrived (WhatsApp, Instagram and Messenger come through the provider; the web chat is handled by the agent runtime), and the reply also stitches together rotated threads. There is no single ordering to offset into, so offering one would return wrong pages. Ask for the number of messages you need.