How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Mem0 memories API

The memories API from Mem0 — 12 operation(s) for memories.

Mem0 memories API is one of 15 APIs that Mem0 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Memories. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 17 operations across 12 paths, and defines 4 schemas. It is described by OpenAPI 3.0.1, at version v1.

Requests are made against a single base URL, https://api.mem0.ai/.

17 operations 12 paths 4 schemas 3 DELETE5 GET7 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v1
Base URL
https://api.mem0.ai
Authentication
API Key
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

Mem0 memories API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API key authentication. Prefix your Mem0 API key with 'Token '. Example: 'Token yourapikey'

Paths & Operations 17

Across 12 paths, the API surfaces 17 operations — 3 DELETE, 5 GET, 7 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

memories 17
GET
/v1/memories/
Get all memories.
memories_list 14 params → 200400
POST
/v1/memories/
Add memories.
memories_create body → 200400
DELETE
/v1/memories/
Delete memories by filter. At least one filter is required — previously omitting all filters silently deleted everything; now it returns a validation error.
memories_delete_all 7 params → 204
POST
/v2/memories/
Get all memories.
memories_list_v2 body → 200400
GET
/v1/memories/events/
memories_events_list → 200
POST
/v1/memories/search/
Perform a semantic search on memories.
memories_search_create body → 200400
POST
/v2/memories/search/
Search memories based on a query and filters.
memories_search_v2 body → 200
POST
/v3/memories/
Get all memories (V3, paginated)
memories_list_v3 2 params body → 200400401
POST
/v3/memories/add/
Add memories (V3)
memories_add_v3 body → 200400401
POST
/v3/memories/search/
Search memories (V3)
memories_search_v3 body → 200400401
GET
/v1/memories/{entity_type}/{entity_id}/
memories_entity_read 2 params → 200
GET
/v1/memories/{memory_id}/
Get a memory.
memories_read 1 param → 200404
PUT
/v1/memories/{memory_id}/
Get or Update or delete a memory.
memories_update 1 param body → 200
DELETE
/v1/memories/{memory_id}/
Get or Update or delete a memory.
memories_delete 1 param → 204
GET
/v1/memories/{memory_id}/history/
Retrieve the history of a memory.
memories_history_list 1 param → 200
PUT
/v1/batch/
Batch update multiple memories (up to 1000) in a single API call.
memories_batch_update body → 200400
DELETE
/v1/batch/
Batch delete multiple memories (up to 1000) in a single API call.
memories_batch_delete body → 200400

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are MemoryInput (19 properties), MemorySearchInput (16 properties), MemorySearchInputV2 (11 properties), MemoryGetInputV2 (6 properties). Each schema is shown below with its type and property counts.

MemorySearchInput
object
16 properties 1 required
MemoryInput
object
19 properties
MemoryGetInputV2
object
6 properties 1 required
MemorySearchInputV2
object
11 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mem0-memories-api-openapi.yml Raw ↑

Other APIs Mem0 publishes across the network.

Mem0 Platform API
Mem0 agents API
Mem0 apps API
Mem0 entities API
Mem0 events API
Mem0 exports API
Mem0 feedback API
Mem0 organizations API
Mem0 Project API
Mem0 projects API
Mem0 runs API
Mem0 stats API
Where this information came from

This is an independent, third-party profile of Mem0 memories API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.