Comma-separated import id’s of a finalised file, as returned by the finalise call.
Example:00000000-0000-0000-0000-000000000000,00000000-0000-0000-0000-000000000000
This call needs to be executed in a loop until its response returns the item(s) id(s) passed in the items parameter.
Comma-separated import id’s of a finalised file, as returned by the finalise call.
Example:00000000-0000-0000-0000-000000000000,00000000-0000-0000-0000-000000000000
Successful response
This endpoint finalizes the upload after all chunks have been uploaded. You need to provide the file ID and details about the file, including its name, size, and the number of chunks it was split into.
For metaproperties that use options (Select, Select2, Autocomplete), modifying an asset’s metaproperty options should be done via option UUID’s for the API to work optimally, sending name or label values will be deprecated in the future. Other metaproperties (Date, Text and Longtext), values can be submitted directly. Be aware that the endpoints described in Step 6 are an Either/Or choice. You should use either the Save as a new asset endpoint to save the uploaded file as a new asset, or the Update existing asset endpoint to update an existing asset with the uploaded file.
Import id of a finalised and processed upload to be saved.
Example:00000000-0000-0000-0000-000000000000
Date/time of publication in ISO08601-format.
Example:2014-06-12T18:53:21.000Z
If audit is set to true you can specify an accessRequestId to batch uploads to the waiting room. The accessRequestId is retrieved in the response of this endpoint, after you save the first asset of your batch.
Example:00000000-0000-0000-0000000000000000
If audit is set to true you can specify an access type to define to which waiting room location the asset is uploaded to. The available locations are: Upload, Edit, Workflow approval (export), Shutterstock and Stock.
Allowed values:uploadeditexportshutterstockstock
Example:upload
Archive date/time of the asset in ISO8601-format.
Example:2014-12-25T10:30:00.000Z
Flags if the asset should be sent to the waiting room.
Example:true
Brand id to save the asset to.
Example:00000000-0000-0000-0000-0000000000000000
Comma-separated category ids of the asset.
Example:00000000-0000-0000-0000000000000000,00000000-0000-0000-0000000000000000
Copyright information of the asset.
Example:Copyright (c) Example corp.
CRC32 checksum of the original file, used for verification.
Example:79764919
Extended asset description.
Example:Extended asset description
Flags if the asset should be Public.
Example:true
Dictionary with (metaproperty) options to set on the asset. Send fields as metaproperty.METAPROPERY_ID with a string of all its (metaproperty) options ids comma-separated.
Example:metaproperty.00000000-0000-0000-0000000000000000=00000000-0000-0000-0000000000000000,00000000-0000-0000-0000000000000000
Name of the asset.
Example:Asset name
DEPRECATED Date/time of publication in linked API user selected locale-format.
Example:05-31-2010
If audit is set to true you can specify a requestor ID (user ID) to identify the user uploading the asset to the waiting room.
Example:00000000-0000-0000-0000000000000000
Comma-separated list of tags of the asset.
Example:scenery,grassland,Holland
Watermark datetime. ISO8601 format: yyyy-mm-ddThh:mm:ssZ.
Example:2014-12-25T10:30:00.000Z
Created
Be aware that the endpoints described in Step 6 are an Either/Or choice. You should use either the Save as a new asset endpoint to save the uploaded file as a new asset, or the Update existing asset endpoint to update an existing asset with the uploaded file.
Asset id to which to save the uploaded file.
Example:00000000-0000-0000-0000-000000000000
Import id of a finalised and processed upload to be saved.
Example:00000000-0000-0000-0000-000000000000
Created
Example:pluploads/api/00000000-0000-0000-0000-000000000000/image.jpeg
Example:pluploads/api/00000000-0000-0000-0000-000000000000/image.jpeg