Use this file to discover all available pages before exploring further.
The attach endpoint associates one or more tags with a set of resources. It accepts a list of tag names — any name that does not yet exist in your organization is created on the fly, and any name that already exists is reused. Every resource list in the request body is then attached to every tag in names.This makes it possible to tag a single resource, apply several tags to a single resource, or apply tags to many resources in a single call.
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 attach. Tags that don’t exist are created automatically.
sources
array of UUIDs
No
Source IDs to tag.
transformations
array of UUIDs
No
Transformation IDs to tag (covers queries, notebooks, and histories).
destinations
array of UUIDs
No
Destination IDs to tag.
visualizations
array of UUIDs
No
Visualization IDs to tag.
layers
array of UUIDs
No
Layer IDs to tag.
folders
array of UUIDs
No
Folder IDs to tag.
tables
array of UUIDs
No
Table IDs to tag.
volumes
array of UUIDs
No
Volume IDs to tag.
At least one resource list must contain at least one ID. Tag names provided in names but missing from the organization are created before the attachment happens.