Move assets to another library
Moves the given assets from one library to another, keeping their IDs and stored files. The caller must own the source library and either own the destination library or be a collaborator on it. A scoped credential must cover both libraries and allow both delete_permanently and write. Moved assets leave the source library’s albums, people, and stacks.
Returns 200 with one result per asset even when some assets could not be moved. Each result describes the asset’s state when the request ran, so repeating a request is safe: an asset already in the destination library is reported as a success.
Returns 409 when a concurrent change interrupted the request; nothing was moved, so retry it unchanged. Returns 503 while moving assets is turned off; retry later.
Authorizations
Gumnut API key (apikey_...) sent as a Bearer token in the Authorization header. Create and manage keys in the Gumnut app, or with the API key endpoints while signed in to it.
Body
Request body for moving assets from one library to another.
Library the assets are in now. The caller must own it.
Library to move the assets into. The caller must own it or be a collaborator on it. Must differ from source_library_id.
Asset IDs (each with the asset_ prefix) to move.
1 - 200 elementsResponse
Successful Response
One result per distinct requested asset ID, in request order.