---
schema_version: "1"
id: 4b46041415dd7965e1c4ece05a19df0bd44e11df29d39e64e34c57052edee9f8
title: Conversation Ingest APIs
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/agentic-memory-context/references/agentic-memory-context-ref/agentic-memory-api-conversation-ingest-apis.md
canonical_url: https://developer.salesforce.com/docs/data/agentic-memory-context/references/agentic-memory-context-api-ref/agentic-memory-api-conversation-ingest-apis.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: e09b8fe477db98cc521485f7801a3485081b8bb4a30ec52f1333c1315efda389
products:
  - Agentic Memory & Context
  - Data 360 Developer Documentation
---
# 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].

## Resource Model

Conversations follow this hierarchical structure.

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

## Key Concepts

- **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.