Cost Reports
cost_reports
Methods
Retrieve a detailed cost report totals for a specified month, which includes both commit and pay-as-you-go (overcommit) prices. Additionally, it provides the spent billing units (e.g., hours or GB) for resources. The "time_to" parameter represents all days in the specified month.
Receiving data from the past hour might lead to incomplete statistics. For the most accurate data, we recommend accessing the statistics after at least one hour. Typically, updates are available within a 24-hour period, although the frequency can vary. Maintenance periods or other exceptions may cause delays, potentially extending beyond 24 hours until the servers are back online and the missing data is filled in.
Total count of the totals
Price status for the UI, type: string
Get a detailed cost report for a given period and specific resources. Requested period should not exceed 31 days.
Note: This report assumes there are no active commit features in the billing plan. If there are active commit features (pre-paid resources) in your plan, use /v1/reservation_cost_report/totals, as the results from this report will not be accurate.
Receiving data from the past hour might lead to incomplete statistics. For the most accurate data, we recommend accessing the statistics after at least one hour. Typically, updates are available within a 24-hour period, although the frequency can vary. Maintenance periods or other exceptions may cause delays, potentially extending beyond 24 hours until the servers are back online and the missing data is filled in.
Get cost report totals (aggregated costs) for a given period. Requested period should not exceed 31 days.
Note: This report assumes there are no active commit features in the billing plan. If there are active commit features (pre-paid resources) in your plan, use /v1/reservation_cost_report/totals, as the results from this report will not be accurate.
Receiving data from the past hour might lead to incomplete statistics. For the most accurate data, we recommend accessing the statistics after at least one hour. Typically, updates are available within a 24-hour period, although the frequency can vary. Maintenance periods or other exceptions may cause delays, potentially extending beyond 24 hours until the servers are back online and the missing data is filled in.
Receiving data from the past hour might lead to incomplete statistics. For the most accurate data, we recommend accessing the statistics after at least one hour. Typically, updates are available within a 24-hour period, although the frequency can vary. Maintenance periods or other exceptions may cause delays, potentially extending beyond 24 hours until the servers are back online and the missing data is filled in.
Billing Reports
cost_reports.billing_reports
Methods
Get a detailed cost report for a given period. Use /v1/cost_report/resources and /v1/cost_report/totals instead, because they provide more accurate results. Note: This report assumes there are no active commit features in the billing plan. If there are active commit features (pre-paid resources) in your plan, use the /v2/billing_report, as the results from this report will not be accurate. Receiving data from the past hour might lead to incomplete statistics. For the most accurate data, we recommend accessing the statistics after at least one hour. Typically, updates are available within a 24-hour period, although the frequency can vary. Maintenance periods or other exceptions may cause delays, potentially extending beyond 24 hours until the servers are back online and the missing data is filled in.
Retrieve a detailed cost report for a specified month. Use /v1/reservation_cost_report/totals instead, which provides more accurate results. This report includes "totals" for both commit and pay-as-you-go (overcommit) prices. Additionally, it provides the spent billing units (e.g., hours or GB) for resources. The "time_to" parameter represents all days in the specified month. Receiving data from the past hour might lead to incomplete statistics. For the most accurate data, we recommend accessing the statistics after at least one hour. Typically, updates are available within a 24-hour period, although the frequency can vary. Maintenance periods or other exceptions may cause delays, potentially extending beyond 24 hours until the servers are back online and the missing data is filled in.