Update metadata on multiple assets
Updates metadata on multiple assets in one transactional call. Each item carries the target asset id and the per-asset change — different fields can be changed on different assets in the same request. Atomic: any per-item validation failure or unknown / cross-user id rejects the whole batch and writes nothing.
Up to 100 items per request; over-cap requests return 422. For a single-asset edit, prefer update_asset — semantically identical but slightly more concise at the call site.
Documentation Index
Fetch the complete documentation index at: https://docs.gumnut.ai/llms.txt
Use this file to discover all available pages before exploring further.
Body
Bulk-update request body — heterogeneous per-asset changes in one call.
List of per-asset updates. Each item carries the target asset id and the change to apply to it; different fields can be changed on different assets in the same request. Up to 100 items per request.
1 - 100 elementsResponse
Successful Response
Acknowledgment body for POST /api/assets/bulk-update.
Empty by design; exists so MCP tools generated from this endpoint have a
real outputSchema. Distinct from DeletionResponse because that
name is purpose-scoped to destructive operations — reusing it on a
non-destructive endpoint would misname the wire shape in OpenAPI and
generated SDKs.
