Create an asset
Authentication
Request
Specifies the upload method for the asset. Use direct to upload a local file or url for a publicly accessible URL.
Specify this parameter to upload a file from your local file system. This parameter is required when method is set to direct.
Local video and audio files support up to 200 MB. Image files support up to 32 MB.
Specify this parameter to upload a file from a publicly accessible URL. This parameter is required when method is set to url.
Public video and audio URLs support up to 4 GB. Image URLs support up to 32 MB.
When set to true, the platform generates an HLS playlist and segments for streaming. Applicable to video and audio assets only.
Default: false.
When set to true, the platform generates thumbnail images from the uploaded content.
Default: false.
Metadata that helps you categorize your assets. You can specify a list of keys and values. Keys must be of type string, and values can be of the following types: string, integer, float, or boolean. Send this value as a JSON-encoded string.
Response
Indicates how you uploaded the asset.
Values:
direct: Uploaded from your local file systemurl: Uploaded from a publicly accessible URLmultipart: Uploaded using the multipart upload flow
Indicates the current processing status of the asset.
A newly uploaded asset starts in the processing status and transitions asynchronously to ready on success or to failed on error, typically within a few seconds to a few minutes. Poll the Retrieve an asset endpoint until the status is ready before you use the asset in downstream workflows.
Values:
processing: The asset is not yet usable. This can mean the upload is still in progress (for example, the platform is still fetching the file from a URL, or a multipart upload has not completed), or the upload has finished and the platform is validating the file. Thetechnical_metadatafield is omitted from the response.ready: The platform validated the asset successfully, and the asset is ready to use.failed: The platform could not process the file. Theerrorfield describes the reason, and thetechnical_metadatafield may be partially populated.
The date and time, in RFC 3339 format (“YYYY-MM-DDTHH:mm:ssZ”), when the asset was created.
User-defined metadata for this asset. This field is absent when no metadata has been set.
Describes where the asset came from. Present only for assets imported through a connector; absent for assets uploaded directly to the /assets endpoint.