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.
View as MarkdownAuthorization
bearer In: header
Query Parameters
Restrict to one team.
uuidResponse Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/cycles"{ "cycles": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "teamId": "a4ede8ba-7c0a-4485-8763-cbd9b282fbec", "number": 0, "name": "string", "startsAt": "2019-08-24", "endsAt": "2019-08-24" } ]}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.
Rename a cycle
The one field of a cycle still changeable by hand. number and dates are roller-owned and no longer accepted here — send them and they are silently ignored, the same as any unknown field on any PATCH body in this service. There is no delete: a cycle cannot be removed once the roller has made it. A name another cycle in the same team already uses is a 409, compared trimmed and case-insensitively; "" clears the name and never collides with another blank one. A cycle's team is immutable, so teamId is not accepted. Cycles in another org read as 404.