Skip to main content
POST
Get metric breakdown aggregation for multiple projects, chains, or products

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
metric_ids
string[]
required

Array of metric IDs to retrieve data for

group_by
enum<string>
required

How to group the results

Available options:
projects,
chains,
chain-project,
chain-product,
chain-market-sector,
market-sector,
product
project_ids
string[]

Optional array of project IDs to filter by

product_ids
string[]

Optional array of product IDs to filter by

chain_ids
string[]

Optional array of chain IDs to filter by

market_sector_ids
string[]

Optional list of market sector IDs to filter by

Example:
interval
enum<string>
default:7d

Length of the aggregation window. Defaults to 7d. The window ends at the latest available date, or the day before end if given.

Ignored when both start and end are given; the window is then the date range [start, end).

Available options:
24h,
7d,
30d,
90d,
180d,
365d,
1095d,
1825d,
ytd,
max
start
string<date>

First date of the aggregation window, inclusive (YYYY-MM-DD).

With end, the window is the half-open range [start, end) and interval is ignored. Without end, the window spans interval days starting on start.

end
string<date>

End of the aggregation window, exclusive (YYYY-MM-DD). Data for this date is not included; must be after start, otherwise the request is rejected with a 400.

For a full calendar month use the first day of the next month, e.g. start=2026-08-01, end=2026-09-01. Without start, the window spans interval days ending the day before end. If omitted entirely, the window ends at the latest date for which data is available. If the day before end has no data yet, the window ends at the latest available date before it.

Response

200 - application/json

OK

data
object[]
errors
object[]

Optional array of errors that occurred during request processing. Only present if some requested entities were not found.

The endpoint returns data for valid entities even when errors are present, allowing partial success.