Asynchronous upload validation
The platform now processes every upload asynchronously. When you create an asset with direct uploads or multipart uploads, the platform returns the asset immediately with the status field set to processing. The asset transitions to the ready status when it is available for use, or to failed when the file is invalid or corrupt. Poll the Retrieve an asset endpoint until the status field is ready before you use the asset.
What changed:
- Polling now applies to every upload. Previously, only public URL uploads larger than 200 MB returned
processingand required polling; smaller uploads returnedreadyin the create response. Now, every upload returnsprocessing, so you must poll before using any asset. - Invalid files now fail asynchronously. Previously, an invalid or corrupt file returned an error at upload time. Now the upload succeeds, and the asset transitions to the
failedstatus, which you detect by polling.
If your integration already polls the asset status until it’s ready, as shown on the Direct uploads and Multipart uploads pages or in the guides, no change is required. Otherwise, poll until the status of the asset is ready before you use it:
Python
Node.js
This change does not require an SDK upgrade.
Technical metadata for assets
The Retrieve an asset and List assets responses now include an object named technical_metadata with details read from the media file: the container format, per-stream video and audio properties, image properties, and derived attributes such as aspect ratio. The platform populates this object asynchronously after the upload completes.
To access this feature, upgrade your SDK to the latest version:
For details, see Retrieve an asset in the API Reference section, or the SDK reference for Python and Node.js.
Higher upload limits
- Multipart uploads now support local videos up to 10 GB (previously 4 GB).
- Image uploads now support files up to 32 MB (previously 5 MB), for both local files and public URLs.
These limits apply when you create an asset. Each model still enforces its own file size and duration limits. For details, see the Upload and processing methods page.
Public video and audio URL uploads remain limited to 4 GB. This change does not require an SDK upgrade.