Write items in bulk
Up to 25 sets and deletes in one call, in one scope.
Not a transaction. Each operation succeeds or fails on its own and is reported separately; the call returns 200 even when some failed. Check every entry’s ok — treating a 200 as “all 25 landed” is the mistake this endpoint invites.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Collection name.
Query Parameters
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.
"contact:jd7x2k3m4n5p6q7r8s9t0abc"
Body
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.
1 - 25 elementsResponse
Every operation was attempted. Inspect each result.
One entry per submitted operation, in order. Check every ok: the call returns 200 even when some operations failed.
