Timeseries endpoints
Both endpoints use the same query language and response format.
The aggregate block
Timeseries queries use anaggregate block to control grouping, time resolution, and computation mode:
groupBy
Controls how results are grouped. Each unique group becomes a separate series in the response.interval
The time resolution of each data point.mode
How values are computed within each interval.
Example: For monthly supply,
stock returns the supply at the end of each month. For monthly mints, flow returns the total minted during each month.
aggregateFunction
Discovering available measures
Every timeseries query requires ameasure_slug filter to specify which metric to retrieve. Use the meta endpoints to discover available measures:
measure_slug field in the response lists all available measures as selectOptions. You can also browse measures in the Data Catalog.
Common measures:
Response format
Timeseries responses differ from list endpoints. Each result contains a measure descriptor, a group descriptor, and an array of points:Examples
Track an asset’s NAV over time
aggregate block is provided, the endpoint defaults to daily granularity grouped by the entity type.
Compare token supply across chains
UsegroupBy: "token" to get a separate series for each on-chain deployment:
Aggregate an entire asset class over time
UsegroupBy: "asset_class" to sum across all assets in a category: