Skip to main content
Costory connects to Datadog billing with a Datadog API key and application key. It uses Datadog usage endpoints and billing endpoints to convert Datadog product usage into cost rows in Explorer. If you also want to import operational metrics from Datadog, see Datadog usage metrics.
Not supported.

​
Data Costory imports

Costory maps Datadog billing rows into Standard Columns, so you can compare Datadog spend with AWS, GCP, Azure, and other billing datasources. Costory includes:
  • Usage-based billing estimates across Datadog products, including infrastructure, APM, logs, and similar usage lines.
  • Per-product cost breakdowns. In Explorer, group by Service name to review each Datadog product.
  • Historical usage data for trend analysis.
Costory does not include:
  • Final Datadog invoices, taxes, credits, or support fees that Datadog does not expose through its billing and usage APIs.
  • Contract-specific pricing terms that are not available through the Datadog APIs.
  • Custom metrics pricing beyond what the Datadog usage API exposes.

​
Why billing_read matters

Datadog usage APIs tell Costory what you used. Datadog billing APIs provide the cost context required to create Datadog billing rows. An API key can pass usage_read and timeseries_query checks while Datadog billing endpoints remain unavailable to Costory. When this happens, Costory can read usage or metric data, but it cannot map Datadog usage into costs.

​
API reference

Costory calls these Datadog Usage Metering API endpoints. The base URL depends on your Datadog site (for example https://api.datadoghq.com for US1). Costory sends your API key and application key on every request.
Use caseEndpointRequired scope
Usage volumes by product familyGET /api/v2/usage/hourly_usageusage_read
Current and previous month cost estimatesGET /api/v2/usage/estimated_costbilling_read
Historical monthly costsGET /api/v2/usage/historical_costbilling_read
hourly_usage returns usage measurements (for example host counts, log volume) that Costory uses to build usage context. estimated_cost covers the current and previous month, with data delayed by up to 72 hours. historical_cost covers earlier months and is typically available by the 16th of the following month.
Billing endpoints (estimated_cost, historical_cost) may return 403 Forbidden even when usage_read works. This is common for accounts billed through AWS Marketplace or GCP Marketplace. See Missing marketplace billing data.

​
Missing marketplace billing data

In rare cases, customers who subscribe to Datadog through AWS Marketplace or GCP Marketplace cannot access Datadog billing data through Costory’s Datadog connector. The connector can still access usage and timeseries data, but Datadog billing data does not appear in Costory after 24 hours. This means Costory can see what was used, but cannot create Datadog billing rows because the billing_read scope is blocked or the billing endpoints are unavailable for the account. This is account-specific and does not mean every has the same limitation. Datadog support can usually confirm the exact reason quickly. If the issue is a Datadog-side bug, they may also provide a workaround that Costory can implement. Use this checklist before contacting Datadog support:
  1. Confirm the application key user has the billing_read scope in Datadog.
  2. Confirm the API key and application key belong to the Datadog site you selected in Costory.
  3. Ask Datadog support why billing_read is blocked for your account.
You can send Datadog support this message: 
We granted usage_read, timeseries_query, and billing_read to the Datadog application key used by Costory.

Usage and timeseries data is available in Costory, but Datadog billing data is still missing after 24 hours.

Why is billing_read blocked for our account?

Could this be related to how our Datadog subscription is linked through AWS Marketplace or GCP Marketplace?

If this is a Datadog-side bug, is there a supported workaround that Costory can implement?
If Datadog confirms that Billing APIs are unavailable for the account, Costory cannot ingest Datadog billing from that key. You can still use Datadog usage metrics as non-cost metrics, but they will not create Datadog cost rows.

Billing Data overview

Review all billing datasources and shared setup concepts.

Datadog usage metrics

Import Datadog timeseries metrics for allocation and analysis.

Explorer

Explore Datadog costs with the rest of your billing data.

Standard Columns

See how Datadog fields map into Costory’s normalized schema.
Last modified on June 24, 2026