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].
Pagination
All three read endpoints follow the same pagination pattern.
- The first response may include
nextPageTokenif more results exist. - To retrieve the next page, replay the same request with the
page_tokenquery parameter set to the value ofnextPageToken. - When
nextPageTokenis absent or empty, iteration is complete.
Example:
First request:
GET /api/v1/agentic/conversations?owner_id=003AB000000XYZ&owner_type=individual
Response includes: "nextPageToken": "eyJvZmZzZXQiOjUwfQ=="
Second request:
GET /api/v1/agentic/conversations?owner_id=003AB000000XYZ&owner_type=individual&page_token=eyJvZmZzZXQiOjUwfQ==
Considerations
- owner_type requirement: Required on List Conversations and List Sessions endpoints. Optional on Get Conversation endpoint.
- agent_id location:
agent_idis 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:
{
"timestamp": "2026-06-18T14:22:00Z",
"error": "CDP_NOT_FOUND",
"message": "Conversation not found",
"path": "/server/api/v1/agentic/conversations/conv-999",
"tenantId": "a360/prod/00D...",
"internalErrorCode": "CONV_404",
"details": {}
}