POST
/
v2
/
memories

Mem0 offers two versions of the get memories API: v1 and v2. Here’s how they differ:

Key difference between v1 and v2 get memories:

Filters: v2 allows you to apply filters to narrow down memory retrieval based on specific criteria. This includes support for complex logical operations (AND, OR) and comparison operators (IN, gte, lte, gt, lt, ne, icontains) for advanced filtering capabilities.

The v2 get memories API is more powerful and flexible, allowing for more precise memory retrieval without the need for a search query.

Authorizations

Authorization
string
header
required

API key authentication. Prefix your Mem0 API key with 'Token '. Example: 'Token your_api_key'

Query Parameters

filters
object

Filters to apply to the memories. Available fields are: user_id, agent_id, app_id, run_id, created_at, updated_at, categories, keywords. Supports logical operators (AND, OR) and comparison operators (in, gte, lte, gt, lt, ne, contains, icontains)

org_name
string

Filter memories by organization name. Will be deprecated soon, use org_id instead.

project_name
string

Filter memories by project name. Will be deprecated soon, use project_id instead.

org_id
string

Filter memories by organization ID.

project_id
string

Filter memories by project ID.

page
integer

Page number for pagination. Default: 1

page_size
integer

Number of items per page. Default: 100

Response

200 - application/json
created_at
string
required
id
string
required
name
string
required
organization
string
required
owner
string
required
total_memories
integer
required
type
enum<string>
required
Available options:
user,
agent,
app,
run
updated_at
string
required
metadata
object