Core Memory Operations
Add Memories
Add facts, messages, or metadata to a user memory store with async processing and event tracking via the V3 additive pipeline.
POST
cURL
Extract and store memories from a conversation using the V3 additive pipeline. The endpoint uses single-pass ADD-only extraction: one LLM call, no UPDATE/DELETE. Memories accumulate over time; nothing is overwritten.
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.
Poll the event status via
GET /v1/event/{event_id}/. Status will be SUCCEEDED or FAILED once processing completes.Memories with
expiration_date remain stored after they expire. Search and get-all hide them by default; pass show_expired: true to include them.Python uses
expiration_date; TypeScript uses expirationDate.Body
application/json
Response
Memory addition queued; returns an event identifier clients can poll via GET /v1/event/{event_id}/.