Granularly analyze customer spend patterns by dynamically slicing and dicing costs across any dimension. This endpoint empowers you to break down spending by granular properties like user, organization, model, region, or any custom event property—even if these aren’t the default groupings on your invoices. Unlike standard invoice breakdowns, this endpoint focuses purely on spend analysis, making helpful for building powerful cost analytics dashboards that show spend before credit/commit application.
Spend-focused invoice data with:
Limitations:
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
If set, list prices will be returned for each contract usage and subscription line item.
RFC 3339 timestamp. Breakdowns will only be returned for time windows that start on or after this time.
RFC 3339 timestamp. Breakdowns will only be returned for time windows that end on or before this time.
If set, all zero quantity line items will be filtered out of the response.
If provided, only invoices with the specified credit type id will be included in the response.
Invoice sort order by issued_at, e.g. date_asc or date_desc. Defaults to date_asc.
date_asc, date_desc The granularity of the breakdowns to return. Defaults to "day".
hour, day, none, HOUR, DAY, NONE, Hour, Day, None A list of keys that can be used to additionally segment the values of the billable metric when making usage queries. Must be valid keys that are present in the billable metrics or an empty list. The value will be ignored and the default keys will be used if: billable metric is MAX type; product uses tiered pricing model; product has quantity rounding enabled; there are contract overrides based on presentation group keys
An object where the keys are the group keys and the values are arrays of group values. If the values is an empty array, the returned usage data will be aggregated across all values for that key. The value will be ignored and the default keys will be used if: billable metric is MAX type; product uses tiered pricing model; product has quantity rounding enabled; there are contract overrides based on presentation group keys
Max number of results that should be returned. For daily and "none" breakdowns, the response can return up to 35 days worth of breakdowns. For hourly breakdowns, the response can return up to 24 hours. If there are more results, a cursor to the next page is returned.
1 <= x <= 100Cursor that indicates where the next page of results should start.