EaserixDocs
DevelopersAPI referenceTasksLabels

Delete a label

Hard delete. The label disappears from every issue it was attached to, unconditionally — unlike a workflow state, a label is never load-bearing for an issue, so there is no in-use guard here and no count in this response. Check issueCount from GET /v1/labels first if that matters to the caller. The deletion is audit-logged with the affected count.

View as Markdown
DELETE
/v1/labels/{id}

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string
Formatuuid

Response Body

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/v1/labels/497f6eca-6276-4993-bfeb-53cbbbba6f08"
{  "message": "string"}

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.

List cycles

Cycles across the org's teams, highest number first. Filter with team_id. No create here. Cycles are roller-owned: a team gets them by turning on `cyclesEnabled` in PATCH /v1/teams/{id}/settings, and a background job creates, numbers and dates every one from that team's cadence. A create route used to exist and was removed — a hand-made cycle could straddle a boundary the scheduler was about to place there itself.