Class CloudCostManagementApi

Create a Cloud Cost Management account for an AWS CUR config.

Create a Cloud Cost Management account for an Azure config.

Create a Cloud Cost Management account for an Google Cloud Usage Cost config.

Create a new custom allocation rule with the specified filters and allocation strategy.

Strategy Methods:

• PROPORTIONAL/EVEN: Allocates costs proportionally/evenly based on existing costs. Requires: granularity, allocated_by_tag_keys. Optional: based_on_costs, allocated_by_filters, evaluate_grouped_by_tag_keys, evaluate_grouped_by_filters.
• PROPORTIONAL_TIMESERIES/EVEN_TIMESERIES: Allocates based on timeseries data. Requires: granularity, based_on_timeseries. Optional: evaluate_grouped_by_tag_keys.
• PERCENT: Allocates fixed percentages to specific tags. Requires: allocated_by (array of percentage allocations).

Filter Conditions:

• Use value for single-value conditions: "is", "is not", "contains", "does not contain", "=", "!=", "like", "not like", "is all values", "is untagged"
• Use values for multi-value conditions: "in", "not in"
• Cannot use both value and values simultaneously.

Supported operators: is, is not, is all values, is untagged, contains, does not contain, in, not in, =, !=, like, not like

Create a new tag pipeline ruleset with the specified rules and configuration

Delete a budget.

Archive a Cloud Cost Management Account.

Archive a Cloud Cost Management Account.

Archive a Cloud Cost Management account.

Delete a custom allocation rule - Delete an existing custom allocation rule by its ID

Delete the specified Custom Costs file.

Delete a tag pipeline ruleset - Delete an existing tag pipeline ruleset by its ID

Get a budget.

Get a specific AWS CUR config.

Get a specific Azure config.

Get a specific Google Cloud Usage Cost config.

Get a specific custom allocation rule - Retrieve a specific custom allocation rule by its ID

Fetch the specified Custom Costs file.

Get a specific tag pipeline ruleset - Retrieve a specific tag pipeline ruleset by its ID

List budgets.

List the AWS CUR configs.

List the Azure configs.

List the Google Cloud Usage Cost configs.

List all custom allocation rules - Retrieve a list of all custom allocation rules for the organization

List the Custom Costs files.

List all tag pipeline rulesets - Retrieve a list of all tag pipeline rulesets for the organization

Reorder custom allocation rules - Change the execution order of custom allocation rules.

Important: You must provide the complete list of all rule IDs in the desired execution order. The API will reorder ALL rules according to the provided sequence.

Rules are executed in the order specified, with lower indices (earlier in the array) having higher priority.

Example: If you have rules with IDs [123, 456, 789] and want to change order from 123→456→789 to 456→123→789, send: [{"id": "456"}, {"id": "123"}, {"id": "789"}]

Reorder tag pipeline rulesets - Change the execution order of tag pipeline rulesets

Update the status (active/archived) and/or account filtering configuration of an AWS CUR config.

Update the status of an Azure config (active/archived).

Update the status of an Google Cloud Usage Cost config (active/archived).

Update an existing custom allocation rule with new filters and allocation strategy.

Strategy Methods:

• PROPORTIONAL/EVEN: Allocates costs proportionally/evenly based on existing costs. Requires: granularity, allocated_by_tag_keys. Optional: based_on_costs, allocated_by_filters, evaluate_grouped_by_tag_keys, evaluate_grouped_by_filters.
• PROPORTIONAL_TIMESERIES/EVEN_TIMESERIES: Allocates based on timeseries data. Requires: granularity, based_on_timeseries. Optional: evaluate_grouped_by_tag_keys.
• PERCENT: Allocates fixed percentages to specific tags. Requires: allocated_by (array of percentage allocations).
• USAGE_METRIC: Allocates based on usage metrics (implementation varies).

Filter Conditions:

• Use value for single-value conditions: "is", "is not", "contains", "does not contain", "=", "!=", "like", "not like", "is all values", "is untagged"
• Use values for multi-value conditions: "in", "not in"
• Cannot use both value and values simultaneously.

Supported operators: is, is not, is all values, is untagged, contains, does not contain, in, not in, =, !=, like, not like

Update a tag pipeline ruleset - Update an existing tag pipeline ruleset with new rules and configuration

Upload a Custom Costs file.

Create a new budget or update an existing one.

Validate a tag pipeline query - Validate the syntax and structure of a tag pipeline query