Update Document Metadata in Batches
Changed onMerge custom_metadata into up to 100 documents in one request. Each item behaves like Update Document Metadata: supplied keys are merged, omitted keys kept, null deletes a key. Returns 200 with one result per item, in order. Envelope, partial success, and unknown outcomes are covered in the Batch Metadata & Relations guide.
Request
- Base URLhttps://api.captain.dev
- URLhttps://api.captain.dev/v3/collections/{collection_name}/documents/metadata/batch
- Authnone declared
Path parameters
Request body
Response
Update Document Metadata in Batches response.
Changes
- warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- warning
- breaking
added
subschema #2subschema #3to the/response propertyoneOflist for the response status - info
removed
subschema #2subschema #3from the/response propertyoneOflist for the response status
- breaking