Legacy calls used to complete the multi-part asset upload
Step 1: Create an upload transaction
The legacy version of this call is /API/UT_UPLOADTRANSACTION/v1.0/CreateTransaction, which can be either POST or GET.
Parameters
The legacy call uses the meta parameter instead of the metadata parameter. Both parameters have the same structure and function.
You can also include these parameters in your call: format, dateformat, and token.
Step 2: Register upload assets
The legacy version of this call is /API/CortexUploader_BO/v1.1/RegisterUploadItems, which can be either POST or GET.
Parameters
The following body parameters’ names differ but have the same function:
| Current call | Legacy call |
|---|---|
transactionID | transaction |
uploaderName | uploader |
skipValidity | skip_validity |
updateincompleteUI | update_incomplete_ut |
cloudCompatible | cloud_compatible |
Response
The legacy call returns a UIRecordId. This is equivalent to the uploadItemID returned by the currently maintained call. The legacy call does not return the identifier, DO_recordID, requestedFileName, or requestedFileSize.
Step 4: Upload each asset chunk
The legacy version of this call is /API/CortexUploader_BO/v1.0/UploadFile, which can be either POST or GET.
Parameters
The following body parameters’ names differ but have the same function:
uploadItemID | UIRecordID |
totalLength | Filelength |
md5 | ChunkMD5 |
Additionally, in this call you must also include the Content-Type header with a value of multipart/form-data.
Step 5: Complete the upload session
There are two legacy versions of this step.
Complete Upload API
The first legacy version of this call is /API/CortexUploader_BO/v1.1/CompleteUpload, which can be either POST or GET.
This call completes an asset upload. The current version of this legacy call also returns the information listed in the currently maintained call. This call uses the legacy parameters listed in the Parameters table .
Note
- The previous version of the API call, version 1.0, did not return information. This version (version 1.1) returns the information listed on the currently maintained call page and is available beginning in Orange Logic Juneau.
CompleteUploadAndIntegrateMetadata API
The second legacy version of this call is /API/CortexUploader_BO/v1.0/CompleteUploadAndIntegrateMetadata, which can be either POST or GET.
This call returns the System Identifier of the asset you uploaded. It uses the parameters listed in the following table.
Parameters
The following body parameters’ names differ but have the same function:
| Current call | CompleteUpload API | CompleteUploadAndIntegrateMetadata API |
|---|---|---|
uploadItemID | UIRecordID | UIRecordID |
fileDigitizedDate | digitizedDate | digitizedDate |
fileDateCreated | dateCreated | dateCreated |
fileDateModified | dateModified | dateModified |
S3PartList | S3uploadparts | N/A |