Skip to main content
POST
Write items in bulk

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

Up to 25 writes and deletes in one call. Operations are NOT atomic: each is reported on its own, and a failure in one does not roll the others back.

ops
object[]
required
Required array length: 1 - 25 elements

Response

Every operation was attempted. Inspect each result.

results
object[]
required

One entry per submitted operation, in order. Check every ok: the call returns 200 even when some operations failed.