Skip to main content
POST
List Inbox

Overview

Returns a paginated list of conversations from the inbox. Filter by category and paginate with the next_cursor value.
This endpoint consumes 1 credit per 10 results returned. The platform returns up to 25 conversations per internal request, so larger total_results values trigger multiple upstream calls automatically. Ignore this if you’re on per-seat pricing: usage is unlimited.

Request

string
required
Your API key for authentication.
string
required
The unique identifier of the account to use.
string
required
Must be "list_inbox".
object
Works for email mailboxes too — the response keeps the same shape (conversations / total_results), each email mapped to a conversation. See Email inbox below.

Response

boolean
Indicates whether the request was successful.
object
object

Sales Nav inbox

InMail threads live in a separate store and never appear in the classic inbox. Set sales_nav: true to read them. Same envelope and paging, with:
  • conversation_id = the Sales Nav thread id, also returned as threadId by Send Message. Only usable with sales_nav: true — the two id spaces are not interchangeable.
  • participant / last_message.sender add recipient_urn, sales_nav_url, connection_level, first_name, last_name; no headline
  • extra: total_message_count, archived, last_message.subject

Email inbox

For an email mailbox, list_inbox returns the same structure (conversations / total_results / next_cursor) — each email is mapped to a conversation. Differences:
  • conversation_id is the thread id (Gmail) — pass it to Get Conversation to fetch the full thread.
  • id is the provider message id — use it with mark_as_read / mark_as_unread / archive / trash and attachment download.
  • participant and last_message.sender carry { name, email } (no profile_url / headline).
  • last_message adds subject; text is the body snippet.
  • Extra per-item fields: message_id, in_reply_to, is_bounce, has_attachments.
Also accepts unread_only, label_ids (read a folder other than INBOX — see list_labels), and cursor pagination (cursor in, next_cursor out) — same model as LinkedIn (Gmail has no offset).
200 (email)

Search (email)

action: "search" searches the whole mailbox and returns the same shape (conversations / total_results / next_cursor). Pass query (Gmail accepts its native syntax, e.g. from:john subject:invoice). Works on Gmail, Outlook and IMAP. Cursor pagination applies.
Request