git.release-assets.listList a release's assets
GET /git/api/repositories/{repoId}/releases/{releaseId}/assetsIAM git:ListReleasesRead
Request syntax
GET /git/api/repositories/{repoId}/releases/{releaseId}/assetsPath parameters
repoIdRequiredstring
Constraints: uuid
releaseIdRequiredstring
Constraints: uuid
Response
200 with the assets: id, name, contentType, sizeBytes, downloadCount, createdAt and downloadUrl.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
[].idAlwaysstring
The asset id[].nameAlwaysstring
The file name it downloads as; unique within the release[].contentTypeAlwaysstring
The content type declared at upload; downloads are always application/octet-stream[].sizeBytesAlwaysnumber
Size of the file, in bytes[].downloadCountAlwaysnumber
How many times it was downloaded[].createdAtAlwaysstring
When it was uploaded (ISO 8601)[].downloadUrlAlwaysstring
The API path that downloads the file
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:ListReleases 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 release-assets list repoId releaseIdcurl -X GET "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/releases/releaseId/assets" \
-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_release-assets_list.