Conversation Retrieval APIs

Retrieve conversation data from Data 360’s real-time hot layer. These read-only endpoints expose conversation Data Graphs stored in the hot layer, providing filtered access to conversation history, entries, and participant information.

Base Path: /api/v1/agentic (also aliased at /personalization/v1/agentic)

Authentication: Bearer JWT token

Required Header: agent_id — Agent identifier

Available in: All editions supported by Data 360. See [Data 360 edition availability].

Note: These are read-only endpoints. All conversation writes must go through the [Conversation Ingest APIs].

All three read endpoints follow the same pagination pattern.

  1. The first response may include nextPageToken if more results exist.
  2. To retrieve the next page, replay the same request with the page_token query parameter set to the value of nextPageToken.
  3. When nextPageToken is absent or empty, iteration is complete.

Example:

First request:

Response includes: "nextPageToken": "eyJvZmZzZXQiOjUwfQ=="

Second request:

  • owner_type requirement: Required on List Conversations and List Sessions endpoints. Optional on Get Conversation endpoint.
  • agent_id location: agent_id is a required header, not a query parameter. All three endpoints reject requests without it.
  • scope parameter: Only available on Get Conversation endpoint. Not supported on List Conversations or List Sessions.
  • Error model: Read API errors return this format: