Skip to main content
The RWA API provides timeseries endpoints for tracking metrics over time and aggregating data across assets, tokens, networks, and asset classes.

Timeseries endpoints

Both endpoints use the same query language and response format.

The aggregate block

Timeseries queries use an aggregate 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 a measure_slug filter to specify which metric to retrieve. Use the meta endpoints to discover available measures:
The 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

When no aggregate block is provided, the endpoint defaults to daily granularity grouped by the entity type.

Compare token supply across chains

Use groupBy: "token" to get a separate series for each on-chain deployment:
This returns one series per chain (e.g., “Ethereum USYC”, “Solana USYC”, “BNB Chain USYC”), so you can see how supply is distributed across networks.

Aggregate an entire asset class over time

Use groupBy: "asset_class" to sum across all assets in a category:
This gives you the total market size of tokenized U.S. Treasuries over time, with one data point per month.

Choosing the right endpoint