List an issue's labels

The labels an issue or a pull request carries, with their colors and descriptions.

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

Issues and pull requests share numbers.

Authentication: Optional. Public data can be read without a token; send one to see what is private.
MCP tool: issue with action labels, and the same inputs
Scope: An access token needs issues:read.

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.

Example request

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

Example response

A successful request answers 200 with:

[
  {
    "name": "bug",
    "color": "d73a4a",
    "description": "Something isn't working",
    "issues": 4,
    "pulls": 1
  },
  {
    "name": "help wanted",
    "color": "008672",
    "description": "Extra attention is needed",
    "issues": 1,
    "pulls": 0
  }
]

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.
422	`invalid`	The input is not valid. `message` says which field and why.