IMPORTANT NOTE
These APIs do not replace the existing v4 APIs yet, and currently only applies to newly uploaded assets still in Draft state (before publishing). Cannot be yet used for Assets that are in Asset Bank and Waiting room.
The request target is the Location response header returned by Upload file initialization. Carry the relevant header information across calls as shown below. After the last chunk is uploaded, the file is automatically finalized.
The
Location Header ValueURL is a placeholder for theLocationheader from the previous call.
Default:1.0.0
The combined length of the previously uploaded chunks. This value can be taken from the Upload-Offset response header of each preceding chunk request.
Default:application/offset+octet-stream
Chunk accepted.
IMPORTANT NOTE
These APIs do not replace the existing v4 APIs yet, and currently only applies to newly uploaded assets still in Draft state (before publishing). Cannot be yet used for Assets that are in Asset Bank and Waiting room.
This step actually starts uploading the file. Send this request to the signed uploadUrl returned by Create upload url. This initializes a resumable (tus) upload. Any file namings have to be base64 encoded/decoded.
The response headers - in particular the Location header - are required for the next call, Upload file chunks.
The
{uploadUrl}path parameter is a placeholder for the signed URL from the previous step.
Default:1.0.0
Total size of the file to upload, in bytes.
Comma-separated key <base64-value> pairs, e.g. filename ZXhhbXBsZS5wbmc=.
Upload initialized. Use the returned Location header for the chunk uploads.
IMPORTANT NOTE
These APIs do not replace the existing v4 APIs yet, and currently only applies to newly uploaded assets still in Draft state (before publishing). Cannot be yet used for Assets that are in Asset Bank and Waiting room.
Creates an empty container, this is the first step to start the file upload and any asset enrichment.
Allowed values:BGBSIBWF
IMPORTANT NOTE
These APIs do not replace the existing v4 APIs yet, and currently only applies to newly uploaded assets still in Draft state (before publishing). Cannot be yet used for Assets that are in Asset Bank and Waiting room.
Once the file is fully enriched and ready it can be published. Depending on the profile permissions of the user, the asset will go directly to the asset bank (upload assets) or to the waiting room (upload assets with mandatory approval)
Optional publish options. If omitted, the asset is published with default settings (forcePublish = false).
When true, forces publication of the asset even if non-blocking validation warnings are present. Defaults to false.
Default:false
Allowed values:BGBSIBWF
IMPORTANT NOTE
These APIs do not replace the existing v4 APIs yet, and currently only applies to newly uploaded assets still in Draft state (before publishing). Cannot be yet used for Assets that are in Asset Bank and Waiting room.
To start uploading a file as an asset, a signed upload url has to be created, which can be used to start uploading the file. Take the generated assetId from the previous {create Asset} as input in the path.