Endpoints
GET
Retrieve memories
POST
Create memory
PATCH
Update memory
DELETE
Delete memory
POST Batch
Create up to 25
Access and availability
Memory endpoints require a Developer API key with the corresponding scope:memories:read for reads and
memories:write for writes. Creating a key is self-service in Developer → API Keys, and creation
records the matching key grant when the key includes a memory scope.
Default memory reads also have a separate, server-owned account readiness gate. A valid, correctly scoped
key can therefore receive 403 while that account is not yet provisioned for Developer Memory API access.
Do not recreate the key in that case; retry after the account is enabled or contact Omi support if it remains
unavailable.
code is the stable programmatic signal. reason provides a diagnostic for the current server-side gate and
must not be treated as a key or scope error.
Get Memories
GET /v1/dev/user/memories
Retrieve your memories with optional filtering
Query Parameters
Query Parameters
- cURL
- Python
- JavaScript
Response Example
Response Example
Response Fields
Response Fields
Create Memory
POST /v1/dev/user/memories
Create a new memory
Request Body
Request Body
- cURL
- Python
- JavaScript
Response Example
Response Example
Create Memories (Batch)
POST /v1/dev/user/memories/batch
Create multiple memories in a single request (max 25)
Request Body
Request Body
Each memory object accepts the same fields as the single create endpoint.
- cURL
- Python
- JavaScript
Response Example
Response Example
Update Memory
PATCH /v1/dev/user/memories/{memory_id}
Update a memory’s content or visibility
Path Parameters
Path Parameters
Request Body
Request Body
At least one field must be provided.
- cURL
- Python
- JavaScript
Response Example
Response Example
Delete Memory
DELETE /v1/dev/user/memories/{memory_id}
Delete a memory permanently
Path Parameters
Path Parameters
- cURL
- Python
- JavaScript
Response Example
Response Example
What Are Memories?
Memories are timeless facts about the user — preferences, relationships, personal details, and notable insights. They are NOT for notes, tasks, or time-sensitive information.
- Good memories: “User is vegetarian”, “User’s sister Sarah lives in Portland”, “User prefers async communication”
- Bad memories: “Meeting on March 15th”, “Call dentist tomorrow” (these are action items or conversations)
Use Case: Store User Preferences
Import known facts and preferences about the user:- Python
- JavaScript
Memory Categories Explained
system
Useful context for the AI: preferences, work details, relationships, logistical info. Example: “User prefers dark mode”
interesting
Shareable, notable facts — things the user would excitedly tell someone at dinner. Example: “User climbed Mount Kilimanjaro”