Add Memories
Add facts, messages, or metadata to a user memory store with async processing and event tracking via the V3 additive pipeline.
Endpoint
- Method:
POST - URL:
/v3/memories/add/ - Content-Type:
application/json
event_id you can poll via GET /v1/event/{event_id}/.
Required headers
Request body
Provide conversation messages for Mem0 to extract memories from. At least one entity ID (user_id, agent_id, app_id, or run_id) is required so the memory is scoped to a session. Entity IDs are accepted at the top level.
Common fields
* At least one entity ID (user_id,agent_id,app_id, orrun_id) is required.
Response
The request is queued for background processing. The response contains anevent_id for tracking status.
GET /v1/event/{event_id}/. Status will be SUCCEEDED or FAILED once processing completes.expiration_date remain stored after they expire. Search and get-all hide them by default; pass show_expired: true to include them.expiration_date; TypeScript uses expirationDate.Body
Conversation messages to extract memories from.
Scope memories to this user.
Scope memories to this agent.
Scope memories to this session / run.
User-supplied metadata to attach to each extracted memory.
Optional expiration date in YYYY-MM-DD format. After this date, memories are hidden from search and get-all unless show_expired is true.
Project-level instructions that guide extraction for this call.
Category catalog for this call. Replaces the project-level list rather than merging with it. Omit to fall back to the project list, then the default catalog.
When false, stores each message verbatim without running the extraction LLM.