Release notes

Introducing asset management

This release introduces new asset management capabilities. It also includes the first set of changes for the deletion safeguards announced on April 8.

HLS streaming and thumbnail generation

You can now request HLS playlists and thumbnail images when creating an asset. Set the enable_hls or enable_thumbnail field to true in your request to the POST method of the /assets endpoint or the POST method of the /assets/multipart-uploads endpoint. The platform generates these in the background. To check progress, call the GET method of the /assets/{asset_id} endpoint and inspect the hls.status and thumbnail.status fields.

New response fields

The following response schemas now include new fields:

• Asset: The size field contains the file size in bytes. The duration field contains the length in seconds for video and audio assets. The method field can now also return multipart for assets uploaded through the multipart upload flow.
• Indexed asset: The asset_id field identifies the source asset, so you can trace an indexed asset back to the asset it was created from.
• Entity: The entity_collection_id field identifies the collection the entity belongs to.

Filename filtering

The GET method of the /assets endpoint now accepts the filename query parameter to filter assets by filename. The match is case-insensitive and supports partial matches.

Look up indexed assets and entities by asset

As announced on April 8, the following are now available:

• The GET method of the /assets/{asset_id}/indexed-assets endpoint lists the indexed assets that reference a given asset.
• The GET method of the /assets/{asset_id}/entities endpoint lists the entities that reference a given asset.
• The force query parameter on the DELETE method of the /assets/{asset_id} endpoint lets you delete the asset even if indexed assets reference it.

On April 26, 2026, delete requests for referenced assets will be denied by default. See the April 8 announcement for required actions.