# PATCH /tags/{id}

Part of the SendHeron REST API. Base URL: `https://api.sendheron.com/api/v1`

Rename or recolor a tag.

```http
PATCH https://api.sendheron.com/api/v1/tags/{id}
Authorization: Bearer <YOUR_API_KEY>
```

**Required scopes:** `contacts:write`

**Success status:** `200`

**Rate limit:** 100/min per key, counted against the organization's WRITE ceiling (400/min).

**Path parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | uuid | yes | Tag UUID. |

**Body parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | New tag name. It must stay unique per workspace. |
| `color` | string | no | Hex value or colour name. |

**Endpoint-specific errors** (beyond the shared error set):

- `409`: Another tag in the workspace already has this name.

> Contacts and templates carrying the tag keep it under its new name, and a sequence triggered by it keeps firing: the tag is referenced by id everywhere, so nothing is re-evaluated. Segment rules on `tags` match by name, so a renamed tag drops out of a segment that names the old one.


---

Rate limits: 100/min per key, counted against the organization's WRITE ceiling (400/min). Both windows are one minute.
