git.labels.createCreate a label
Request syntax
POST /git/api/repositories/{repoId}/labels
{
"name": "string",
"color": "string",
"description": "string"
}Path parameters
repoIdRequiredstring
Constraints: uuid
Request body
nameRequiredstring
The label name, unique in the repository
Constraints: 1-50 chars
colorOptionalstring
Six hex digits, e.g. d73a4a; grey (6b7280) when absent
descriptionOptionalstring
What the label is for
Constraints: max 200 chars
Response
201 with the label. 409 when a label of that name exists.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
The label idorgIdAlwaysstring
The organization it belongs torepoIdAlwaysstring
The repository it belongs tonameAlwaysstring
The label name, unique within the repositorycolorAlwaysstring
Six hex digits, without #descriptionAlwaysstring, may be null
What the label means; null when none was givencreatedAtAlwaysstring
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:ManageLabels 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 create repoId --name examplecurl -X POST "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/labels" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_labels_create.