Moves an asset to a different folder.

post

https://localhost:44395/api/admin/asset/{id}/move

Behavior: Moves the specified asset to the target folder provided in the batch model. The asset retains its identity and metadata but is relocated in the folder hierarchy. The batch model should include the destination folder ID in the action arguments.

Authorization: Requires a valid Bearer token.

Side Effects: The asset is relocated to the new folder. The search index is updated to reflect the new location.

Error Scenarios: Returns 400 if the request body is missing. Returns 401 if the caller is not authenticated.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

uuid

required

The unique identifier of the asset to move.

Body Params

The batch payload containing the destination folder and optional arguments.

batchAction

object | null

contentDefinitionId

uuid | null

schemaName

string | null

targetIds

array of uuids | null

targetIds

userId

uuid

actionArguments

object | null

Note that we convert all incoming keys to lower first char to help with serialization for JSON later

resolverExempt

boolean | null

Headers

content-type

string

enum

Defaults to application/json-patch+json

Generated from available request content types

Allowed:

Responses

Language

Credentials

Bearer

JWT

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The asset was moved successfully.

400The request body is missing or invalid.

401Caller is not authenticated.