Assets

Submit a new version of an existing asset

Creates a new version of the asset identified by asset_id. asset_id may be the media_source_id of any version in the chain — the endpoint resolves the version-1 anchor automatically. The new asset is queued for analysis and can be tracked with GET /v1/assets/{asset_id} using the asset_id returned here. All versioning logic (auto-incrementing version number, flipping latest_version) is handled server-side. Provide exactly one of file_id (uploaded file) or url (web link).

patch/v1/assets/{asset_id}

Request

  • Base URL: https://api.blee.com
  • URL: https://api.blee.com/v1/assets/{asset_id}
  • Auth: HTTP bearer

Path parameters

asset_idstring required

The media_source_id of any existing version of the asset (returned in files[] or urls[] of the bundle response).

Request body

OR

Example request

{
  "subject": {
    "email": "user@company.com"
  }
}

Response

New version accepted and queued for analysis.

asset_idstring required

The media_source_id of the newly created version.

media_source_idstring required
version_one_media_source_idstring required

The media_source_id of the first version in this chain.

status'queued' required
dashboard_urlstring required
poll_interval_secondsnumber required

Changes

No recorded changes to this operation across all 1 revision of this API.