curl --request GET \
--url https://api.orq.ai/v2/memory-stores/{memory_store_key}/memories \
--header 'Authorization: Bearer <token>'{
"object": "list",
"data": [
{
"_id": "<string>",
"entity_id": "<string>",
"created": "<string>",
"updated": "<string>",
"store_id": "<string>",
"metadata": {},
"workspace_id": "<string>",
"documents_count": 123,
"created_by_id": "<string>",
"updated_by_id": "<string>"
}
],
"has_more": true
}Retrieves a paginated list of memories for the memory store
curl --request GET \
--url https://api.orq.ai/v2/memory-stores/{memory_store_key}/memories \
--header 'Authorization: Bearer <token>'{
"object": "list",
"data": [
{
"_id": "<string>",
"entity_id": "<string>",
"created": "<string>",
"updated": "<string>",
"store_id": "<string>",
"metadata": {},
"workspace_id": "<string>",
"documents_count": 123,
"created_by_id": "<string>",
"updated_by_id": "<string>"
}
],
"has_more": true
}Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The unique key identifier of the memory store
A limit on the number of objects to be returned. Limit can range between 1 and 50, and the default is 10
1 <= x <= 200A cursor for use in pagination. starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 20 objects, ending with 01JJ1HDHN79XAS7A01WB3HYSDB, your subsequent call can include after=01JJ1HDHN79XAS7A01WB3HYSDB in order to fetch the next page of the list.
A cursor for use in pagination. ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 20 objects, starting with 01JJ1HDHN79XAS7A01WB3HYSDB, your subsequent call can include before=01JJ1HDHN79XAS7A01WB3HYSDB in order to fetch the previous page of the list.
Search query to filter memories by entity_id
Successfully retrieved the list of memories.
list Show child attributes
Flexible key-value pairs for custom filtering and categorization. Clients can add arbitrary string metadata to enable future filtering of memory access based on their specific needs (e.g., user segments, topics, contexts, or any custom taxonomy).
Show child attributes
The number of memories in the entity
Was this page helpful?