> This page is for version v1.3 (default).
> For other versions, use one of these documentation indexes:
> - v1.3 (default): https://docs.twelvelabs.io/v1.3/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.twelvelabs.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.twelvelabs.io/_mcp/server.

## 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`](/v1.3/api-reference/upload-content/direct-uploads/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:

Review your code for calls to the [`DELETE`](/v1.3/api-reference/upload-content/direct-uploads/delete) method of the `/assets/{asset_id}` endpoint.

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

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.

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

Test your changes before April 26, 2026.

### Support

For migration assistance, contact our support team at [support@twelvelabs.io](mailto:support@twelvelabs.io).