# Promote Asset Version

Promote an existing version of an Asset to be its current version. The Asset is identified by an Object ID or File ID in the request path; the version to promote is identified by the fileId in the request body.

Promoting a version creates a new current version from the nominated one, and carries the Asset's existing collection memberships and relationships onto it.

The user requesting the promotion must have access to the Asset.

Note on response shape: the data property carries the newly created asset-version record. Its fields are not enumerated in the handler's type definitions, so they are not documented here — see GET /asset/{id} for the Asset shape.

Endpoint: POST /asset/{id}/version/promote
Version: 1.5
Security: ApiKeyAuth, BasicAuth

## Header parameters:

  - `X-API-Key` (string, required)
    Customer-specific API key required to invoke API.

  - `Authorization` (string, required)
    Provided by Authentication Token creation operation

  - `Content-Type` (string, required)
    Enum: "application/json"

## Path parameters:

  - `id` (string, required)
    Object ID or File ID of the asset whose version is being promoted.

## Request fields (application/json):

  - `fileId` (string, required)
    File ID of the existing version to promote to current.
    Example: "8cd2c221-6a91-4dc6-9379-d55dca9d5313"

## Response 200 fields (application/json):

  - `status` (string)
    Example: "success"

  - `message` (string)
    Example: "Asset version promoted successfully"

  - `data` (object)
    The newly created asset-version record. Field-level shape is not declared in the handler's types; see GET /asset/{id} for the Asset shape.

## Response 401 fields (application/json):

  - `status` (string)
    Example: "error"

  - `message` (string)

## Response 403 fields (application/json):

  - `status` (string)
    Example: "error"

  - `message` (string)