Skip to main content
GET
List chat session history

Merge entries

Merged histories remain in their original sessions. The primary and each source receive an internal session_merged event containing the merge identifier and source/primary links. New customer messages received in a merged source produce a merged_session_message event in the final primary, referencing the original source session and message UUID. For the Merge sessions workflow action, event.merge.actor.type is workflow, with the workflow ID in event.merge.actor.id and the run ID in event.merge.actor.workflow_run_id. Manual Inbox merges use agent with agentId; direct API merges use api. The events export also includes the workflow and run in its top-level actor and details fields. These entries are internal to your team. Do not display them in customer-facing transcripts. Fetch the referenced source history to display its current message content; a reference does not make the source contact a recipient of replies sent from the primary.

Paused AI services

When paused AI services hand a session to your team, an ai_services_paused event follows its handoff event. An incoming call that rings your team instead of the AI for the same reason gets the ai_services_paused event too. Like the merge entries, it is internal to your team.

Retention erasures

When session retention erases a session, its history gets a session_erased_by_system_due_to_retention_threshold event. Its optional reason says which rule erased it, for example Closed for 30 days or No activity for 90 days. The session’s other messages return [REDACTED] as their content. This entry is internal to your team. Do not display it in customer-facing transcripts.

Deleted replies

A reply an agent deleted from the inbox is omitted, as are deleted internal notes. The deletion itself is not listed here; the events export records it.

Email recipients

Message events with stored email headers include an optional event.email object:
These are the addresses recorded for that individual message, not the session’s current reply recipients. from is the original sender address when available; to and cc are address arrays and can be empty. The original sender can differ from the session contact when a connected inbox honors Reply-To. The object is omitted for non-email messages and messages without stored email headers, including older imported messages. Missing metadata does not mean the original email had no recipients. Companion can read these details through its existing session-history tool. BCC recipients are not included. Receiving a blind copy does not reveal other hidden recipients; the original visible To and CC recipients remain useful when your inbox receives a blind copy.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

session_id
string
required

The unique identifier of the chat session

Query Parameters

cursor
string

Pagination cursor to fetch the next set of results

Response

Default Response

items
object[]
required
next
string | null
required