PATCH
/tags/{id}PATCH /tags/{id}
Rename or recolor a tag.
Request
curl -X PATCH 'https://api.sendheron.com/api/v1/tags/{id}' \
-H 'Authorization: Bearer <YOUR_API_KEY>' \
-H 'Content-Type: application/json'Required scopes
The key must carry these:
- contacts:write
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. |
Responses
Returns 200 on success.
- 400
- The payload failed validation, or the request is not valid for the current state.
messagesays which kind of refusal it is, and for a payload that failed validation (validationFailed) thedescriptionnames the field and says what was wrong with it in words, e.g. "domain: domain must be a bare hostname such as acme.com, with no scheme, path, or port". An id in the path that is not a UUID answersinvalidUUIDon every route. - 401
- Missing or invalid API key.
- 403
- Valid key, but it does not carry the required scope.
messageisapiKeys.insufficientScopesand thedescriptionnames both halves of the problem: "Missing required scope(s): X. This key holds: Y." Neither is a secret, since the required scopes are on this page and the held ones are your own credential, and a bare "Forbidden" costs a debugging pass to work out which of the two it was. - 404
- No such record in this workspace. An id belonging to a different workspace returns this too, never a 403, because the API will not confirm that a record exists outside the workspace your key was issued in. Read it as "not yours or not there" rather than as "definitely gone".
- 409
- A duplicate, or an idempotency key reused with a different payload.
- 429
- Either rate-limit ceiling was exceeded.
messageistooManyRequests, and theRetry-Afterheader says how many seconds until the window rolls. - 409
- Another tag in the workspace already has this name.
Rate limits
100/min per key, counted against the organization's WRITE ceiling (400/min). Both windows are one minute.