monitoring.incidents.listOpen incidents, and those resolved in the last `days` days, newest first
GET /monitoring/api/status-pages/{id}/incidentsIAM monitoring:DescribeStatusPagesRead
Request syntax
GET /monitoring/api/status-pages/{id}/incidentsPath parameters
idRequiredstring
Constraints: uuid
Query parameters
daysOptionalnumber
1–365, default 30
Constraints: integer
Response
200 with up to 200 incidents, each { id, title, impact, status, componentIds, startedAt, resolvedAt (null while open), updates }, updates being { id, status, body, createdAt }. 404 for a missing page and for one the caller may not describe.
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 monitoring:DescribeStatusPages 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 monitoring incidents list idcurl -X GET "https://console.platform.deutschecloud.app/monitoring/api/status-pages/id/incidents" \
-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_monitoring_incidents_list.