Query items by field

curl --request POST \ --url https://api.zavu.dev/v1/memory/collections/{collection}/query \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "where": { "field": "status", "op": "eq", "value": "shipped" } } '

{ "items": [ { "key": "ORD-12345", "rev": 3, "createdAt": "2023-11-07T05:31:56Z", "updatedAt": "2023-11-07T05:31:56Z", "value": { "status": "shipped", "total": 42.5 }, "expiresAt": "2023-11-07T05:31:56Z" } ], "nextCursor": "<string>" }

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

collection

string

required

Collection name.

Query Parameters

scope

string

Which scope to address: contact:<contactId>, conversation:<conversationId>, or omitted for the project scope.

Note the asymmetry with POST /v1/memory and POST /v1/memory/search, which take the scope in the request BODY as scope plus contactId/conversationId. Every other Memory endpoint takes it here. Scope as a query-string value: contact:<contactId>, conversation:<conversationId>, the literal project, or omitted for project scope.

Only the SHAPE of the id is validated, never its existence — the partition already carries your project, so an id that matches nothing simply addresses an empty scope rather than returning 404.

Example:

"contact:jd7x2k3m4n5p6q7r8s9t0abc"

Body

application/json

Look items up by an indexed field instead of by key.

where

object

required

One condition on one indexed field. between bounds are inclusive and must be the same type.

Show child attributes

limit

integer

default:50

Required range: 1 <= x <= 100

cursor

string

Response

Matching items.

items

object[]

required

Show child attributes

nextCursor

string | null