---
schema_version: "1"
id: 2c872ccc8e470322565f1e34103b0a9f88272cc804ce29d5f6e30669177d78d7
title: Memory 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-memory-apis.md
canonical_url: https://developer.salesforce.com/docs/data/agentic-memory-context/references/agentic-memory-context-api-ref/agentic-memory-api-memory-apis.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: d0a97497e778ae7a0e792cb060a6768c6f11afca1c64314ed8987a86f297c783
products:
  - Agentic Memory & Context
  - Data 360 Developer Documentation
---
# 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](https://help.salesforce.com/s/articleView?id=data.c360_a_dc_editions.htm&type=5).

> **Note:** The write methods (`POST` and `DELETE`) 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. Out-of-the-box categories use a `sys_` prefix, such as `sys_PROFILE_FACT` and `sys_PROFILE_PREFERENCES`. Custom categories are free-form and use no prefix. |

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