billing.savings.dismissKeep a finding, with a reason, for good or until a date
Request syntax
POST /billing/api/cost-findings/dismiss
{
"key": "string",
"reason": "string",
"until": "string"
}Request body
keyRequiredstring
The finding’s key, e.g. idle-machine:ec2_instance/i-abc
Constraints: 3-300 chars, /^[a-z-]+:[^\s]+$/
reasonRequiredstring
Why it stays — shown to everyone
Constraints: 3-500 chars
untilOptionalstring
Bring it back after this instant; omitted = keep for good
Constraints: datetime
Response
200 with { success: true } and no data. Dismissing a key again replaces its reason and date; a well-formed key is stored even when no such finding exists today.
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 billing:DismissCostFinding 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 billing savings dismiss --key example --reason examplecurl -X POST "https://console.platform.deutschecloud.app/billing/api/cost-findings/dismiss" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"key":"example","reason":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_billing_savings_dismiss.