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-.
Channel types
The Type column maps the underlying channel value to a readable label.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.

