billing.budget-proposals.approve

Approve a proposal: stop or scale down every resource it names

POST /billing/api/budgets/action-proposals/{id}/approveIAM billing:ApproveBudgetActionChanges stateDestructive

Each stop runs through its own route with your credential, so it also needs ec2:StopInstances, rds:StopDBInstance or autoscaling:UpdateAutoScalingGroup on that resource and is audited as yours. A resource someone already stopped is `skipped`. Only a pending proposal can be approved, once (409 otherwise). Start the resources again, or set the group’s sizes back to `previous`, to undo.

Request syntax

POST /billing/api/budgets/action-proposals/{id}/approve

Path parameters

  • idRequired

    string

    Constraints: uuid

Response

200 once every stop has been tried, with the proposal (status done) and its items, each with result { status done, skipped or failed, detail, at }. 403 when you may stop none of them: nothing is stopped and the proposal stays pending. 409 when it is not pending (decided, or expired); 404 when it is not in your organization.

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:ApproveBudgetAction 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 budget-proposals approve id

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