Skip to main content
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.
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.

Request body

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.

Response

The endpoint returns the list of tags that were matched by names 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

Authorizations

x-api-key
string
header
required

API Key authentication. Format: 'x-api-key: api_key'

Body

name
string
required
Maximum string length: 255

Response

200 - application/json
id
string<uuid>
required
read-only
name
string
required
Maximum string length: 255
created_at
string<date-time>
required
read-only
updated_at
string<date-time>
required
read-only