GetEstimatedCostByOrg
Retrieve estimated costs for multi-org and single root-org accounts within Datadog. Access data for the current or previous month, customizable by date range, view type, and connected accounts.
Instructions
Get estimated cost across multi-org and single root-org accounts.
Estimated cost data is only available for the current month and previous month
and is delayed by up to 72 hours from when it was incurred.
To access historical costs prior to this, use the /historical_cost endpoint.
This endpoint is only accessible for parent-level organizations.
Query Parameters:
view: String to specify whether cost is broken down at a parent-org level or at the sub-org level. Available views are
summaryandsub-org. Defaults tosummary.start_month: Datetime in ISO-8601 format, UTC, precise to month:
[YYYY-MM]for cost beginning this month. Either start_month or start_date should be specified, but not both. (start_month cannot go beyond two months in the past). Provide anend_monthto view month-over-month cost.end_month: Datetime in ISO-8601 format, UTC, precise to month:
[YYYY-MM]for cost ending this month.start_date: Datetime in ISO-8601 format, UTC, precise to day:
[YYYY-MM-DD]for cost beginning this day. Either start_month or start_date should be specified, but not both. (start_date cannot go beyond two months in the past). Provide anend_dateto view day-over-day cumulative cost.end_date: Datetime in ISO-8601 format, UTC, precise to day:
[YYYY-MM-DD]for cost ending this day.include_connected_accounts: Boolean to specify whether to include accounts connected to the current account as partner customers in the Datadog partner network program. Defaults to
false.
Responses:
200 (Success): OK
Content-Type:
application/json;datetime-format=rfc3339Response Properties:
data: Response containing Chargeback Summary.
Example:
{
"data": [
"unknown_type"
]
}400: Bad Request
Content-Type:
application/json;datetime-format=rfc3339Response Properties:
errors: A list of errors.
Example:
{
"errors": [
"Bad Request"
]
}403: Forbidden - User is not authorized
Content-Type:
application/json;datetime-format=rfc3339Response Properties:
errors: A list of errors.
Example:
{
"errors": [
"Bad Request"
]
}429: Too many requests
Content-Type:
application/json;datetime-format=rfc3339Response Properties:
errors: A list of errors.
Example:
{
"errors": [
"Bad Request"
]
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | No | Datetime in ISO-8601 format, UTC, precise to day: `[YYYY-MM-DD]` for cost ending this day. | |
| end_month | No | Datetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]` for cost ending this month. | |
| include_connected_accounts | No | Boolean to specify whether to include accounts connected to the current account as partner customers in the Datadog partner network program. Defaults to `false`. | |
| start_date | No | Datetime in ISO-8601 format, UTC, precise to day: `[YYYY-MM-DD]` for cost beginning this day. **Either start_month or start_date should be specified, but not both.** (start_date cannot go beyond two months in the past). Provide an `end_date` to view day-over-day cumulative cost. | |
| start_month | No | Datetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]` for cost beginning this month. **Either start_month or start_date should be specified, but not both.** (start_month cannot go beyond two months in the past). Provide an `end_month` to view month-over-month cost. | |
| view | No | String to specify whether cost is broken down at a parent-org level or at the sub-org level. Available views are `summary` and `sub-org`. Defaults to `summary`. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Response containing Chargeback Summary. |