jDID THIS ARTICLE SOLVE YOUR ISSUE?
Let us know so we can improve!
Let us know so we can improve!
Memory APIs
Create, read, update, and delete memory entries in Data 360’s Agentic Memory system. The Memory APIs let you curate profile facts and preferences programmatically, alongside the memories that the automatic extraction pipeline generates.
Base Path: /api/v1/agentic/memory (JWT) or /server/api/v1/agentic/memory (mTLS)
Authentication: Bearer JWT token
Available in: All editions supported by Data 360. See Data 360 edition availability.
Note: The write methods (
POSTandDELETE) share the same query parameters and headers. Only the request body differs.
Common Query Parameters
The Memory APIs share these query parameters.
| Parameter | Type | Required | Description |
|---|---|---|---|
| profile_id | String | Yes | Profile ID of the Individual or User. Not derived from authentication. |
| profile_type | String | Yes | Type of profile. Values: individual, employee. |
| category | String | Yes | Partition key for the memory entries, such as PROFILE_FACT. Accepts free-form values, so you can add new categories. |
Request Headers
| Header | Required | Description |
|---|---|---|
| Authorization | Yes | Bearer JWT token. |
| agent_id | No | Registered agent API name. Optional, because clients can also call these APIs. |
| x-sfdc-cdp-tenant-id | No | Tenant ID. Required for mTLS calls. |
| x-sfdc-dataspace | No | Data space. Used for mTLS calls when agent_id is absent. |
j