Skip to main content
POST
Get Conversation

Overview

Returns messages from a specific conversation, ordered from most recent to oldest. Identify the conversation by conversation_id or by passing a profile_url (the conversation with that user is resolved automatically). Pagination is cursor-based — pass the next_cursor returned by a previous call to fetch older messages.
This endpoint consumes 1 credit per 10 messages returned. Ignore this if you’re on per-seat pricing: usage is unlimited.
For an email mailbox, pass the conversation_id from List Inbox to fetch the whole thread. The response keeps the same shape (messages[], total_message_count, next_cursor), each email mapped to a message — sender_info carries { name, email, is_me }, and each message adds id (provider message id), subject, message_id, and has_attachments / attachments[] ({ filename, mime_type, size, attachment_id, message_id }, downloadable via the attachment endpoint). Gmail and Outlook are supported; generic IMAP falls back to the inbox listing.

Request

string
required
Your API key for authentication.
string
required
The unique identifier of the account to use.
string
required
Must be "get_conversation".
object
required

Response

boolean
Indicates whether the request was successful.
object
object

Sales Nav conversations

Set sales_nav: true and pass the Sales Nav thread id — from List Inbox with sales_nav: true, or the threadId returned when the InMail was sent. profile_url is not supported, so conversation_id is required. Messages keep the classic shape and order (newest first), plus:
  • sender_info.is_me and sender_info.recipient_urn
  • subject and attachments, only when present — attachments use the same shape as in webhook message events, fetched via Download Attachment
  • content_flag — DELETED when the message was deleted; text is then empty
  • edited_at — only on edited messages
  • message_type: INMAIL, INMAIL_ACCEPT, INMAIL_REPLY, MESSAGE
last_seen_message is replaced by conversation_id, type, archived and participants (everyone but you).
Sales Nav has no message cursor: a thread returns its count most recent messages and never issues a next_cursor (cursor is ignored). To read further back, raise count — compare it with total_message_count to know whether you have the whole thread.