Get Conversation Messages API
The Get Conversation Messages API loads the message history for a single Instagram or Twitter/X conversation, most recent first. Use the conversationId returned by List Conversations, together with the platform and accountId query parameters, to retrieve the messages array for that conversation.
Get Conversation Messages API overview
This endpoint loads the messages in one conversation, most recent first. Supported platforms are instagram and twitter. On Twitter/X each read call costs 1 credit; Instagram reads are free, as specified in the captured contract. Start from the conversationId returned by List Conversations so the request targets a single conversation rather than a list of conversations.
Request
Send a GET request to {{API_BASE_URL}}/v1/messages/{conversationId} with the x-access-key header set to YOUR_ACCESS_KEY. The conversationId is a required string path parameter described as the platform conversation ID. See the Get Conversation Messages request example for the exact request line and header.
Path parameters
The path parameter conversationId identifies the conversation whose history you want. It is required, its type is string, and it should be the platform conversation ID obtained from List Conversations. Use the conversationId that corresponds to the selected platform and account so the request loads the intended history.
Query parameters
The platform query parameter is required and accepts instagram or twitter. The accountId query parameter is required and is the Integration ID from list_integrations. The limit parameter is optional, is an integer, and controls the maximum number of messages to return, from 1 to 100, with a default of 25. The after parameter is optional and is a string pagination cursor from a previous response. See the Query parameters table for the full field map distinguishing required and optional parameters.
Response
The response contains success, a messages array, and nextCursor. Each entry in messages contains id, text, from with id and name, and timestamp. The messages are ordered most recent first. See the Get Conversation Messages response example for the exact response shape, and see the Response field map table for each field.
Pagination
To load older messages, pass the nextCursor value from a response as the after query parameter in the next request, keeping conversationId, platform, accountId, and limit consistent unless you intentionally change the page size. Repeat this until nextCursor is null, which means no more pages. See the Pagination worked example using nextCursor as after for the step-by-step sequence, and check that you are not reusing a cursor from a different conversation or account.
| Parameter | Type | Required | Description |
|---|---|---|---|
| conversationId | string | Yes | Platform conversation ID |
Exact captured contract; conversationId is the platform conversation ID.
| Parameter | Type | Required | Description |
|---|---|---|---|
| platform | string | Yes | instagram or twitter |
| accountId | string | Yes | Integration ID from list_integrations |
| limit | integer | No | Max messages to return (1-100, default 25) |
| after | string | No | Pagination cursor from a previous response |
Exact captured contract; limit range is 1-100 with default 25.
| Field | Type (inferred from captured JSON example) | Description |
|---|---|---|
| success | boolean (inferred) | Indicates whether the request succeeded |
| messages | array (inferred) | Message history for the conversation, most recent first |
| messages[].id | string (inferred) | Message identifier |
| messages[].text | string (inferred) | Message text |
| messages[].from.id | string (inferred) | Sender identifier |
| messages[].from.name | string (inferred) | Sender name |
| messages[].timestamp | string (inferred) | Message timestamp |
| nextCursor | string or null (inferred) | Pass as after in the next request; null means no more pages |
Exact captured response shape; messages are most recent first. Types are inferred from the captured JSON example, not explicitly typed in source tables.
Frequently asked questions
What do I need before calling Get Conversation Messages API?
Use the conversationId returned by List Conversations, supply platform as instagram or twitter, and supply accountId as the Integration ID from list_integrations. The limit parameter is optional and defaults to 25.
How does pagination work with nextCursor and after?
Pass the nextCursor value from the previous response as the after query parameter in the next request. When nextCursor is null, there are no more pages to load.
What fields does each message contain?
The messages array is returned most recent first. Each message includes id, text, from with id and name, and timestamp.
GET {{API_BASE_URL}}/v1/messages/{conversationId}
x-access-key: YOUR_ACCESS_KEY
# Query parameters (illustrative values)
# platform=instagram
# accountId=YOUR_ACCOUNT_ID
# limit=25
# after=YOUR_CURSOR{
"success": true,
"messages": [
{
"id": "mid.aWdfbXNnXzk5OQ",
"text": "An example comment.",
"from": { "id": "17841400000000001", "name": "Jane Doe" },
"timestamp": "2026-08-05T16:40:00.000Z"
},
{
"id": "mid.aWdfbXNnXzk5OA",
"text": "An example comment.",
"from": { "id": "17841400000000000", "name": "Your Brand" },
"timestamp": "2026-08-05T16:41:30.000Z"
}
],
"nextCursor": null
}GET /v1/messages/{conversationId}
x-access-key: YOUR_ACCESS_KEY