EaserixDocs
DevelopersAPI referenceTasksLabels

Create a label

Color defaults to "#95a2b3". The team must belong to the caller's org (else 404). `name` is stored trimmed and must be unique within the team, compared case-insensitively — a name already in use is a 409, whatever colour it is sent with. Two different teams may each use the same name.

View as Markdown
POST
/v1/labels

Authorization

bearer
AuthorizationBearer <token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/labels" \  -H "Content-Type: application/json" \  -d '{    "teamId": "a4ede8ba-7c0a-4485-8763-cbd9b282fbec",    "name": "string"  }'
{  "label": {    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "teamId": "a4ede8ba-7c0a-4485-8763-cbd9b282fbec",    "name": "string",    "color": "string"  }}

List labels

Labels across the org's teams, ordered by name. Filter with team_id.

Update a label

Rename or recolour. Omitted fields keep their stored value. A label's team is immutable, so teamId is not accepted — moving a label would detach it from every issue that carries it. A name another label in the same team uses is a 409, compared trimmed and case-insensitively; a label keeping its own name is not a collision. Unlike a cycle, a label has no number to fall back on, so a blank name is a 400 and never clears it. An empty color resets it to the default "#95a2b3". Editing a label changes it on every issue it is attached to. Labels in another org read as 404.