ecr.scan-results.getFetch the findings of one scan
Request syntax
GET /ecr/api/scan-results/{scanId}Path parameters
scanIdRequiredstring
Constraints: uuid
Response
200 with the scan: id, manifestId, repositoryId, status (pending, running, completed, failed), triggeredBy (auto, manual), startedAt, completedAt, summaryCritical, summaryHigh, summaryMedium, summaryLow, summaryUnknown (null until completed), error (set when failed), createdAt, and findings, the scanner's (Trivy) full JSON output as a string (null until the scan completes). 404 for a scan id that is not the organization's.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
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 ecr:GetScanResults 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 ecr scan-results get scanIdcurl -X GET "https://console.platform-development.deutschecloud.app/ecr/api/scan-results/scanId" \
-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_ecr_scan-results_get.