billing.savings.list

What could be saved a month, resource by resource, with the action

GET /billing/api/cost-findingsIAM billing:GetCostAndUsageRead

Kinds: idle-machine, oversized-machine, oversized-database, stopped-server, unattached-volume, unused-elastic-ip. Each finding: evidence (one sentence with the numbers), monthlySaving (EUR, 8 places, after discounts; 0 for elastic IPs, not billed yet), confidence (medium when memory is not measured), and the action as an API operation id with method, path and body. `rules` spells out every rule. Dismissed findings are listed separately with who kept them and why.

Request syntax

GET /billing/api/cost-findings

Response

200 with { generatedAt, findings (open, largest saving first), dismissed, totalMonthlySaving, byKind [{ kind, count, monthlySaving }], rules }. Each finding: key (what dismiss takes), kind, kindLabel, resource { type, id, name, href, tags, projects, creator }, evidence, monthlySaving, billedToday, note, confidence, action, resize { from, to } or null.

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:GetCostAndUsage 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 list

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_billing_savings_list.