monitoring.status-pages.updateChange a status page’s title, description or address
Request syntax
PATCH /monitoring/api/status-pages/{id}
{
"slug": "string",
"title": "string",
"description": "string"
}Path parameters
idRequiredstring
Constraints: uuid
Request body
slugOptionalstring
The host label: {slug}.status.{root}. 3–63 lower-case letters, digits, dashes; unique across the platform (409 when taken); reserved words (www, status, api, …) are refused with 400. Moves the page to the new address; unchanged when omitted
titleOptionalstring
One line, up to 120 characters; unchanged when omitted
descriptionOptionalstring
Plain text, up to 1000 characters; null removes it, unchanged when omitted
May be null.
Response
200 with the page as list describes it. 400 for a reserved slug; 409 when the address is another page’s; 404 when the organization has no such page.
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:UpdateStatusPage 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 status-pages update idcurl -X PATCH "https://console.platform.deutschecloud.app/monitoring/api/status-pages/id" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_monitoring_status-pages_update.