Step 2: Register upload assets

Register each asset you’ll upload as part of the transaction created in the previous step

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

After you create a transaction ID for your upload session, you’ll register the list of assets to upload during the upload session. Registering your assets allows Orange Logic to determine which asset a file chunk belongs to. This step also allows you to define the folder hierarchy for the assets in Orange Logic. You can structure this call to mirror the folder hierarchy in Orange Logic or your local folder hierarchy. Folders that do not already exist in the Orange Logic platform will be created.

This page shows the POST method, but you can also use GET.

Response

This call returns one object for each asset you register. For each asset, the response lists:

  • status: The asset’s current upload status.
  • startposition: The starting position of the first byte in the asset. This is always zero.
  • uploadItemID: The asset’s upload identifier. You will use this ID in subsequent calls to associate file chunks with the asset they belong to and notify Orange Logic when all of an asset’s file chunks are uploaded.
  • identifier: The identifier of the asset that will be created or updated when this upload is complete.
  • dO_recordID: The Record ID of the asset that will be created or updated when this upload is complete.
  • requestedFileName: The asset’s filename.
  • requestedFileSize: The asset’s file size.
Body Params
string
required

The transaction ID created with the Create Upload Transaction API in Step 1.

string

The Record ID of the folder you’ll upload the asset to.

files
array of objects
required

A JSON-serialized array of objects representing the assets to upload.

files*
string
Defaults to Cortex Uploader

Name of the upload method you’re using.

boolean
Defaults to false

When false, OrangeDAM runs a validity check on files to prevent user errors and ensure they are safe to process. When true, OrangeDAM skips this check.

boolean
Defaults to false

This parameter is currently unused.

string

The user RecordID for web upload.
This parameter is set by the client uploader application. You do not need to enter anything in this parameter.

boolean
Defaults to false

When false, upload files are sent to the local buffer (the server that hosts the web application) and cannot use a cloud bucket as a buffer.
When true, upload files can use a cloud bucket as a buffer. To use a cloud buffer, there are some constraints depending on the cloud service provider. For example, for Amazon S3 the chunk size must be:

  • Constant for all the chunks (except the last chunk).
  • Between 5MB and 5GB (no min size for the last chunk).
  • The asset can contain no more than 10,000 chunks.

Response

Language
Credentials
OAuth2
URL
LoadingLoading…
Response
Choose an example:
application/json