Reading Messenger conversation history through the API
A Facebook Page's Messenger history is read with GET /{page-id}/conversations?platform=messenger, which lists conversation IDs with their last update time, then GET /{conversation-id}?fields=messages for the message IDs and GET /{message-id} for each message's sender, recipient, text and attachments. Meta returns details for the 20 most recent messages of a conversation, and the calls need a Page token with pages_messaging.
easyCoexistence forwards a Page's new Messenger messages to your endpoint as they arrive, and send_social_dm replies inside the 24-hour window, from Claude, ChatGPT or your own code.
Only the 20 most recent messages in a conversation return details; older ones return an error saying the message was deleted.
Conversations API calls an app can make per Facebook Page.
Conversations in the Requests folder that have not been active for this long are left out of API results.
The Page task the person behind the token must be able to perform to read conversations.
Error for too many Messenger API calls to a Page account; Meta says to wait a bit and try again.
How do you list a Page's conversations?
With GET /{page-id}/conversations, setting platform to messenger. The result holds a data array of conversation IDs, each with updated_time, the time the last message was added, and a paging object; Meta's reference notes that time-based pagination is not available on this endpoint, so follow the paging object to move through the list.
GET /{page-id}/conversations?platform=messenger
{
"data": [
{ "id": "<CONVERSATION_ID>", "updated_time": "<TIME>" },
{ "id": "<CONVERSATION_ID>", "updated_time": "<TIME>" }
],
"paging": { ... }
}How do you find one person's conversation?
Add user_id, set to the person's Page-scoped ID, to the same request. Meta answers with the ID of the conversation between the Page and that person, which is the shortest path from a messages webhook, where the PSID arrives as sender.id, to the history behind it:
GET /{page-id}/conversations?platform=messenger&user_id=<PSID>
{ "data": [ { "id": "<CONVERSATION_ID>" } ] }How do you read the messages in a conversation?
In two steps. GET /{conversation-id} with fields=messages returns the conversation's message IDs, each with created_time, the most recent first; then GET /{message-id} with the fields you need, such as id, created_time, from, to, message and reply_to, returns the content of one message. The default fields are id and created_time, and a field with no data is left out of the response.
Which fields can you read?
A conversation and a message expose different fields. These are the ones Meta's references list for Page messaging:
- Conversation: id,
updated_time, participants with their ID, name and email, messages, andis_owneronce Conversation Routing is on. - Message: id,
created_time, from and to, each with an ID, name and email, and message, the text, empty when there is none. - attachments: files, images and videos with their CDN URLs, and
is_unsupported, returned only when a message contains unsupported content. - reactions,
reply_towith the mid it answers andis_self_reply, and shares for shared posts and reels. - tags: the message's folder and source, such as inbox, read or source:chat.
How far back can you read?
As far as the conversation goes for IDs, but not for content. Meta's guide says the conversation endpoint returns all message IDs in a conversation, while details come back only for the 20 most recent messages; asking for an older one returns an error that the message has been deleted. Conversations in the Requests folder that have been inactive for 30 days are not returned at all.
Which permissions and tasks does it need?
A Page access token from someone who can perform the MESSAGING or MODERATE task on the Page, with the pages_manage_metadata, pages_read_engagement and pages_messaging permissions. Reading conversations with people who have no role on the app, the Page or the business requires Advanced Access, which Meta grants through App Review.
What limits apply to the calls?
Meta's rate limits give the Conversations API 2 calls a second per Page, and calls past a limit come back as 613 or as 80006, There have been too many messenger api calls to this Page account. A Page that hits Meta's high-volume limit, such as sending more than 40 messages a second, cannot list its conversations until volume falls, though a single conversation can still be read for new messages.
When should you use the API instead of webhooks?
For the past. Webhooks deliver new messages as they happen, and Meta notes that past notifications cannot be queried later, so the Conversations API is how an integration reads what came before it started listening, or catches up after downtime. With Conversation Routing on, the is_owner field narrows the list to the conversations the app is responsible for answering, which Meta suggests for recovery after downtime.
How does easyCoexistence read Messenger history?
It does not read history. The Page connects with the pages_messaging, pages_manage_metadata and pages_read_engagement permissions, but no tool calls the Conversations API, and Page tokens are not handed out. New messages reach your endpoint through set_social_webhook_destination as they arrive, passed on without a copy, so your own system keeps the history it needs.
Common mistakes
- Expecting message content in the list call. The conversation endpoint returns message IDs; read each message's fields from /{message-id}.
- Counting on the whole history. Details stop at the 20 most recent messages, so store what you need from webhooks as messages arrive.
- Polling for new messages. At 2 calls a second per Page, a poll loop soon meets the rate limit, while the messages webhook delivers them as they happen.
- Paging conversations by date with since and until. Time-based pagination is not available on the conversations endpoint; follow the paging object instead.
It has no tool for the Conversations API, so earlier history is read in the Page inbox. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Does the Conversations API include the Page's own messages?
Yes. A message's from and to fields name the person or the Page, so a conversation's messages include both sides.
Can I read Messenger conversations without App Review?
For people with a role on the app or the Page, Standard Access is enough. Conversations with anyone else need Advanced Access, granted through App Review.
Can the Conversations API send replies?
No. Meta's conversation reference says the edge cannot publish; replies go through the Send API at /{page-id}/messages.
Does easyCoexistence store my Messenger conversations?
Not by default. Forwarded events are passed on without keeping a copy; with an automation switched on, message text is kept for 7 days and automation run logs for 30 days.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on