GET /core/conversations, which returns conversations across all four channels in one response.
How the list works
The inbox renders as one infinitely scrolling table. As you scroll to the bottom, it loads the next page automatically using cursor-based pagination — there are no page numbers. Each page is fetched with acursor, and results are ordered by created_at (newest first).
Click any row to open that conversation’s detail page in a new browser tab. The inbox stays open in the original tab so you can keep scanning while you read a transcript.
Pending WebRTC sessions are hidden. Conversations in the
token_created status (a web session that has a token but has not started) are excluded from the list, so you only see real interactions.Columns
The table shows the following columns. Values render only when present; missing values display as-.
| Column | Description |
|---|---|
| Copy link | A copy icon that copies a direct link to the conversation to your clipboard. |
| Play | For conversations with status completed or transferred that have a recording, an inline play button streams the recording without leaving the page. |
| Agent | The agent that handled the conversation, with an external-link icon that opens the agent (and its version, when known) in a new tab. |
| Caller ID | The caller’s identifier (user_id). Guest web visitors (ids that begin with guest_) show as Guest, with the full id in a tooltip. For email, a +N bubble appears when the thread has additional participants beyond the caller and the agent; hover it to see their addresses. |
| Caller Name | The caller’s name, when known. |
| Agent Number | The agent’s number or address that the conversation came in on or went out to. |
| Direction | Inbound or Outbound. |
| Status | The conversation status, formatted in title case (for example Completed, Transferred). |
| Summary | A generated summary of the conversation. Hover to read the full text. |
| Duration | The length of the conversation, formatted as hours, minutes, and seconds. |
| Date | The date the conversation was created, in your local time zone. |
| Time | The time the conversation was created, in your local time zone. |
| Type | The channel: Phone Call, Web Chat, Email, or Text. |
Channel types
The Type column maps the underlying channel value to a readable label.| Channel value | Label |
|---|---|
telephone | Phone Call |
webrtc | Web Chat |
email | |
text | Text |
What you can do next
Open a conversation
Read the full transcript, listen to recordings, and review metadata on the detail page.
Search and filter
Narrow the inbox by agent, direction, status, channel, date range, duration, and more.
Monitor live calls
Watch conversations as they happen in real time.
Permissions and data access
Reading the inbox requires one of theconversations:read, conversations:read_sensitive, or conversations:manage scopes. Without conversations:read_sensitive, the API returns only a safe subset of columns, so sensitive fields are hidden from accounts that lack that scope.
When you call the API directly, user PATs (pat_) must also send the X-Anyreach-Org header; org API keys (ak_) carry their organization implicitly.