# Delete a tag

Source: https://kirora.io/docs/api/reference/deleteTag

`DELETE /v1/tags/{id}`

Requires an API key with the `tags:write` scope. [About keys and scopes](https://kirora.io/docs/api/reference/authentication)

Works with integration, agent and partner keys.

A repeat after success returns 404 or 409: treat that as done. [About idempotency](https://kirora.io/docs/api/reference/idempotency)

Deletes the tag and takes it off every item; the items themselves are kept. Refused with 409 `IN_USE` while a rule names it (a segment, campaign audience, journey, goal, or a block condition in a design), since the rule would then match nobody. `details.usedBy` lists the first 50 of each kind (`segments`, `campaigns`, `journeys`, `goals`, `templates`, `sharedBlocks`), with `hasMore` when a kind holds more. Merge it into another tag instead to keep those rules working.

## Path parameters

- `id` (string, required, uuid) — The tag's id.

## Header parameters

- `Kirora-Workspace` (string, optional, pattern `^[A-Za-z0-9._:-]{1,128}$`) — Partner keys only: the child workspace to act in, by the external id the partner gave it. Without it, a partner key acts in its own workspace. Any other key that sends it is refused with 403, and an unknown workspace is 404.

## Returns

Returns `204 No Content` with an empty body. It can also return `409 Conflict`; see the statuses below. Otherwise returns an error; [Errors](https://kirora.io/docs/api/reference/errors) lists every code and which to retry.

Statuses:

- `204 No Content`: The tag was deleted.
- `409 Conflict`: The request conflicts with current state — a duplicate unique value, or a resource whose status does not allow this operation.

## Example

```bash
curl -X DELETE https://api.kirora.io/v1/tags/018f2a4e-6b1c-7d3e-9f40-37386ae05a6b \
  -H "Authorization: Bearer $KIRORA_API_KEY"
```