accept-budget-suggestion

dci accept-budget-suggestion id

Marks the suggestion as accepted and links it to an existing budget. Create the budget first via POST /analytics/v1/budgets, then pass its id as budgetId. The budget must belong to your account.

Request

Content-Type: application/json

Schema

{
  "type": "object",
  "description": "Links a budget suggestion to an existing budget.",
  "required": [
    "budgetId"
  ],
  "properties": {
    "budgetId": {
      "type": "string",
      "description": "ID of the budget (created via POST /analytics/v1/budgets) to link this suggestion to."
    },
    "editedBeforeAccept": {
      "type": "boolean",
      "description": "Whether the customer edited the suggested values before accepting."
    }
  }
}

Output

OK - The suggestion was accepted and linked to the budget.

By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.

Field	Type	Description
budgetId	string	ID of the budget the suggestion was linked to.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "budgetId": {
      "type": "string",
      "description": "ID of the budget the suggestion was linked to."
    }
  }
}

Errors

On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.

HTTP status	Exit code	Error code	Meaning
400	30	VALIDATION_ERROR	The arguments or request body were rejected. Review the command's flags and payload.
401	10	AUTHENTICATION_FAILED	Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY.
403	11	PERMISSION_DENIED	The DoiT user or the active customer context does not have access.
404	20	RESOURCE_NOT_FOUND	The requested resource does not exist. Check the identifier argument.
500	40	API_SERVER_ERROR	The API failed to process the request. Retryable; contact DoiT support if it persists.

Aliases: acceptbudgetsuggestion