Remove labels from an issue

Take labels off an issue or a pull request: label for one, labels for several, or neither for all of them.

DELETE/repos/{owner}/{name}/issues/{number}/labels

The labels stay on the repository. Returns its labels now.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: issue with action remove_labels, and the same inputs
Scope: An access token needs issues:write.
Also at: DELETE /repos/{owner}/{name}/issues/{number}/labels/{label}

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.
`number`	integer	Yes	The number shown after the #. Issues and pull requests share one sequence.

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`label`	string	No	The label’s name, e.g. “good first issue”. URL-encode spaces in the path.
`labels`	array of strings	No	Instead of label: several to take off. With neither, all of them.

Example request

curl -X DELETE https://api.g1t.sh/repos/flagon-io/hello/issues/12/labels \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

[]

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.