Use this file to discover all available pages before exploring further.
The detach endpoint removes the association between one or more existing tags and a set of resources. The tag itself is not deleted — only the links between the tag and the resources in the request body are removed. Tag names that do not exist in the organization are ignored silently.The request body is identical to Attach Tags: a list of tag names and one or more resource ID lists.
The interactive API Playground on this page is generated from the OpenAPI schema and may only show the base Tag fields. The canonical request body is the one documented below (names plus the per-resource ID arrays), and the response is an array of tags, not a single object.
Tag names to detach. Names that don’t exist in the organization are skipped.
sources
array of UUIDs
No
Source IDs to untag.
transformations
array of UUIDs
No
Transformation IDs to untag (covers queries, notebooks, and histories).
destinations
array of UUIDs
No
Destination IDs to untag.
visualizations
array of UUIDs
No
Visualization IDs to untag.
layers
array of UUIDs
No
Layer IDs to untag.
folders
array of UUIDs
No
Folder IDs to untag.
tables
array of UUIDs
No
Table IDs to untag.
volumes
array of UUIDs
No
Volume IDs to untag.
Unlike attach, the detach endpoint does not create tags on the fly. If a name in names is not already present in your organization it is simply skipped.