Get the transcript of a conversation

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.

GET
/v1/conversations/{conversationId}/messages

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.

Authorization

AuthorizationBearer <token>

The organization API key, sent as Authorization: Bearer <key>.

In: header

Path Parameters

conversationId*string

Query Parameters

limit?integer

How many messages to return. Maximum 200.

Range1 <= value <= 200
Default50

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/conversations/string/messages"
{  "data": [    {      "content": "string",      "conversationId": "string",      "createdAt": "string",      "direction": "string",      "id": "string",      "messageType": "string",      "senderName": "string"    }  ],  "total": 0}