# Update assets' lifecycle stage

Move a set of Asset resources from one Asset.lifecycleStatus.state to another.

The Asset resources to be added to the batch job are specified using the AssetSearch criteria language or by a simple set of ids

> If you are selecting by search criteria you must explicitly include criteria describing the state you are moving from in order to account for the fact that the Dash API will only return Assets in the 'LIVE' state by default. See the request examples for more.

Endpoint: POST /asset-lifecycle-transition-batch-jobs
Version: 2.0.0
Security: bearerToken

## Request fields (application/json):

  - `selector` (any)

  - `transition` (string)
    The transition. Generally describe the state moving from and to.
    Enum: "STAGED_TO_PENDING_APPROVAL", "STAGED_TO_LIVE", "PENDING_APPROVAL_TO_LIVE", "LIVE_TO_BINNED", "BINNED_TO_LIVE"

## Response 4XX fields (application/json):

  - `timestamp` (string)
    The datetime that the error occurred in ISO offset format
    Example: "2021-02-16T16:21:58.640+00:00"

  - `status` (integer)
    The HTTP status code of the error
    Example: 401

  - `error` (string)
    The title of the error
    Example: "Unauthorized"

  - `message` (string)
    A more detailed error message

  - `path` (string)
    The path that was called which led to the error
    Example: "/folder-settings"