---
schema_version: "1"
id: 58d69f7301c77fd1e885e410a968b884edb69a24b50b93530401582b61f4c603
title: Memory Management
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/agentic-memory-context/guides/agentic-memory/agentic-memory-memory-management.md
canonical_url: https://developer.salesforce.com/docs/data/agentic-memory-context/guide/agentic-memory-memory-management.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: e36ea921550002c4e9256c02894e924d160b0e761ef8b9d25364566e4a0dafb7
products:
  - Agentic Memory & Context
  - Data 360 Developer Documentation
---
# Memory Management

Create, retrieve, update, and delete memory entries programmatically using the Memory Management APIs. These APIs supplement the automatic extraction pipeline by enabling you to curate knowledge manually. They also serve as the underlying mechanism for UI-based memory curation where users view, edit, and delete facts and preferences.

> **Note:** Memory Management APIs operate alongside the automatic extraction pipeline. Both can write to the same scope. For endpoint details, request schemas, and complete field reference, see [Agentic Memory & Context API Reference](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Agent-Configuration).

## API and Pipeline Interaction

When both the Memory Management API and the automatic extraction pipeline write to the same scope, these behaviors apply.

- **API writes take priority:** The system cancels any active extraction batch for that scope when an API write occurs.
- **Pipeline re-runs:** The extraction pipeline re-runs with the updated state on its next cycle.
- **Entry tagging:** API-created entries are tagged with author type `USER_API` to distinguish them from system-generated entries.

## Unified Individual Memory Retrieval

When your data space uses Unified Individual, retrieve memories across all member individuals in a single call using the unified flag. Data 360 performs these operations.

- Resolves the unified identity.
- Fans out reads across all member individuals.
- Returns a merged result set with the source individual ID on each entry.

This enables agents to access the complete memory profile across all identities that comprise a unified individual.

## Considerations

- Data 360 scopes each entry to one individual and one memory type.
- You can't create conversation-scoped memories using the API. The `conversationId` scope is reserved for system-generated summaries.
- Expired entries aren't physically deleted. You can recover them by updating the `validTo` field.
- Data 360 stores freeform fields with no type validation.
- Deletion is permanent and you can't undo a deletion.

## See Also

- [_Salesforce Developer_: Agentic Memory & Context API Reference](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Agent-Configuration)