Agentic Memory & Context API Reference

Use the Agentic Memory and Context APIs to send agent conversation data to Data 360, retrieve conversation history, and assemble governed context payloads for your agents. These APIs support the full runtime lifecycle of an agent interaction—from ingesting messages and traces to composing memory-grounded prompts for LLM consumption.

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

The Agentic Memory and Context API is organized into three functional groups.

• Conversation Ingest APIs: Create conversations and sessions, manage participants, ingest messages and traces, and close sessions and conversations. Use these endpoints to feed the memory extraction pipeline.
• Conversation Retrieval APIs: Read-only endpoints for listing conversations and sessions and retrieving full conversation Data Graphs. Use these endpoints to inspect ingested conversation state.
• Context API: Retrieve assembled context payloads composed from memories, conversation history, and profile data. Use these endpoints at agent runtime to ground LLM prompts.

All endpoints require a Bearer JWT token in the Authorization header.

Most endpoints also require the agent_id header, which identifies your registered agent and resolves the data space for the request. The Get Context endpoint is the exception: it accepts agent_id as a query parameter.

Before you call any endpoint, complete the setup steps in Agent Registration. In particular, your agent must be registered, and your data space must be configured for Agentic Memory.