Skip to navigation
Get Started

Release notes

April 8, 2026

Deleting referenced assets will be denied by default (Effective April 26, 2026)

Currently, you can delete any asset, even if an indexed asset references it. Starting on April 26, 2026, the platform will deny delete requests for referenced assets by default, returning a 409 Conflict error.

These changes will roll out in two phases:

  • April 15, 2026: The following become available, and you can begin updating your deletion workflow:
    • The GET method of the /assets/{asset_id}/indexed-assets endpoint
    • The force query parameter on the DELETE method of the /assets/{asset_id} endpoint
  • April 26, 2026 (breaking change): Delete requests for referenced assets are denied by default.

Actions required

Complete these steps before April 26, 2026:

1

Review your code for calls to the DELETE method of the /assets/{asset_id} endpoint.

2

Before deleting, call the GET method of the /assets/{asset_id}/indexed-assets endpoint to check whether any indexed assets reference the asset.

3

If references exist, either remove them before deleting the asset or add force=true as a query parameter to delete it anyway. Use force=true only when your application intends to bypass the reference check and delete the asset regardless of existing references.

4

Update your error handling to account for 409 Conflict responses on delete requests.

5

Test your changes before April 26, 2026.

Support

For migration assistance, contact our support team at support@twelvelabs.io.