DID THIS ARTICLE SOLVE YOUR ISSUE?
Let us know so we can improve!
Let us know so we can improve!
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.
nextPageToken if more results exist.page_token query parameter set to the value of nextPageToken.nextPageToken is absent or empty, iteration is complete.Example:
First request:
1GET /api/v1/agentic/conversations?owner_id=003AB000000XYZ&owner_type=individualResponse includes: "nextPageToken": "eyJvZmZzZXQiOjUwfQ=="
Second request:
1GET /api/v1/agentic/conversations?owner_id=003AB000000XYZ&owner_type=individual&page_token=eyJvZmZzZXQiOjUwfQ==agent_id is a required header, not a query parameter. All three endpoints reject requests without it.1{
2 "timestamp": "2026-06-18T14:22:00Z",
3 "error": "CDP_NOT_FOUND",
4 "message": "Conversation not found",
5 "path": "/server/api/v1/agentic/conversations/conv-999",
6 "tenantId": "a360/prod/00D...",
7 "internalErrorCode": "CONV_404",
8 "details": {}
9}