git.labels.listList labels
GET /git/api/repositories/{repoId}/labelsIAM git:ListIssuesRead
Request syntax
GET /git/api/repositories/{repoId}/labelsPath parameters
repoIdRequiredstring
Constraints: uuid
Response
200 with the labels, by name: id, name, color, description and createdAt.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
[].idAlwaysstring
The label id[].orgIdAlwaysstring
The organization it belongs to[].repoIdAlwaysstring
The repository it belongs to[].nameAlwaysstring
The label name, unique within the repository[].colorAlwaysstring
Six hex digits, without #[].descriptionAlwaysstring, may be null
What the label means; null when none was given[].createdAtAlwaysstring
When it was created (ISO 8601)
Checked against the handlers: every route test validates their answers against this schema.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow git:ListIssues on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud git labels list repoIdcurl -X GET "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/labels" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_labels_list.