cURL
Tags
Detach Tags
Remove one or more tags from sources, transformations, destinations, and other catalog resources.
POST
cURL
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.
Request body
| Parameter | Type | Required | Description |
|---|---|---|---|
names | array of strings | Yes | 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. |
Response
The endpoint returns the list of tags that were matched bynames and from which the resources were detached.
Example: detach one tag from a single source
Example: detach multiple tags from one transformation
Example: batch detach tags across sources, transformations, and destinations
Python example: remove a tag from every destination that currently carries it
Related
- Attach Tags — create the inverse association.
- List Tags — confirm which tags currently exist.
Authorizations
API Key authentication. Format: 'x-api-key: api_key'
Body
Maximum string length:
255