assets

Update metadata on multiple assets

Changed on

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.

For a single-asset edit, prefer update_asset — semantically identical but slightly more concise at the call site.

post/api/assets/bulk-update

Request

  • Base URL: https://api.gumnut.ai
  • URL: https://api.gumnut.ai/api/assets/bulk-update
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Request body

Response

Successful Response

BulkUpdateAssetsResponse required

Empty acknowledgment returned by bulk_update_assets.

Changes

    • info

      added the new optional request property ///

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • breaking

      response property detail list-of-types was widened by adding types string to media type application/json of response 422

    • info

      the response property became required for the status