List messages

Fetch messages for a specific conversation, with cursor-based pagination and ordering control.

Pagination: pass pagination.nextCursor from a prior response back as the cursor query param to fetch the next page. The cursor is opaque; do not parse or construct it client-side.

Sort order: defaults to asc (oldest first, chat style). For the "show me the latest messages" pattern, pass ?sortOrder=desc&limit=N. Twitter, Instagram, Telegram, WhatsApp and Reddit honor the requested order from the local message store. For Facebook and Bluesky, the upstream APIs only return newest-first and have no order parameter — sort order is best-effort and only reverses items within a single page (pages still walk newest→oldest). The response field sortOrderApplied tells you what was actually applied.

Reddit threads are paginated client-side because Reddit's API has no per-thread cursor. Very long threads may be upstream-truncated by Reddit's inbox/sent windows (~100 most-recent items each); this is a Reddit platform limitation.

Instagram and Facebook conversations include history from before the account was connected, replayed from Meta. That replay covers the 500 most recent messages per conversation: a longer thread keeps its newest 500 and older messages are not retrievable. Messages that arrived after the account was connected are unaffected. Replayed messages are stored as already read and emit no webhooks.

Twitter/X limitation: X's encrypted "X Chat" messages are not accessible via the API. Conversations where the other participant uses encrypted X Chat may only show your outgoing messages. See the list conversations endpoint for more details.

This endpoint is read-only and does NOT mark messages as read or send read receipts. To mark a conversation read (and send WhatsApp blue ticks on eligible accounts), call POST /v1/inbox/conversations/{conversationId}/read.