Conversation Ingest APIs

Send agent conversation data to Data 360 to build persistent memory and enable context retrieval. The Conversation Ingest APIs support the full lifecycle of an agent interaction, from creation through message ingestion to session closure.

Base Path: /api/v1/agentic (JWT) or /server/api/v1/agentic (mTLS)

Authentication: Bearer JWT token

Required Header: agent_id — Your registered agent’s API name

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

Conversations follow this hierarchical structure.

1Conversation (conversationId)
2├── ownership: conversationOwnerId + ownerType (individual | employee)
3├── channel: { type: web|chat|voice|sms|email|other, id }
4└── Session (sessionId)
5    ├── Participants[]: { id, type, role, startTime?, endTime?, orgId? }
6    └── Entries[]
7        ├── category: Message | Trace | Entry
8        ├── Message: content required, type ∈ { user_message, agent_response }
9        └── Trace: payload in variable, type ∈ { agent_reasoning, tool_call, tool_result }

• Conversation: The highest-level container for an interaction. Can contain multiple sessions for handoffs or pauses.
• Session: A continuous interaction within a conversation. Multiple sessions support agent transfers.
• Participant: An individual, employee, or agent involved in the session.
• Entry: A single interaction record (message or trace) within a session.