deploy.deployments.eventsRead the activity feed of a deployment, including release output
Request syntax
GET /deploy/api/deployments/{id}/eventsPath parameters
idRequiredstring
Constraints: uuid
Query parameters
sinceOptionalstring
Only events created after this time (ISO 8601), to follow the feed
Constraints: datetime
Response
200 with `data`: up to 200 events, oldest first — id, orgId, resourceType, resourceId, createdAt, level, phase, source and message.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
[].idAlwaysstring
Event id[].orgIdAlwaysstring
Organization[].resourceTypeAlwaysstring
Kind of resource, deployment here[].resourceIdAlwaysstring
The deployment’s id[].sourceAlwaysone of control_plane, machine
control_plane or machine[].levelAlwaysone of info, warn, error
info, warn or error[].phaseAlwaysstring, may be null
Stage, e.g. build or release; null if none[].messageAlwaysstring
What happened[].createdAtAlwaysstring
When
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 deploy:DescribeApp 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 deploy deployments events idcurl -X GET "https://console.platform-development.deutschecloud.app/deploy/api/deployments/id/events" \
-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_deploy_deployments_events.