Skip to main content
Every timeseries endpoint identifies a series by a key in the path or in series. For entity-keyed models that key is the primary key of a row in a tabular model, usually a UUID such as b204e48e-9812-43e6-a00b-5fcfd40e04a2. Slugs and symbols are accepted by the tabular row endpoint but not by the timeseries path: a request such as /query/timeseries/blockchains/1d/solana returns 200 with an empty points array and no entity, not a 404. Resolve the identifier first.
1

Look up the row

2

Put the primary key in the timeseries path

/query/timeseries/blockchains/1d/b204e48e-9812-43e6-a00b-5fcfd40e04a2

​
Lookup table

One row per lookup: the timeseries models that share a key, the path parameter that carries it, the request that resolves it, and the identifiers that request accepts. Generated from the catalog, so it is complete for every model in this reference.

​
Keys that are plain names

Aggregate models (sectors, sub-sectors, exchange types, countries and regions) key their series by a display name rather than an id. Where the model allows it, call the multi-series endpoint without series and read series[].key; those values are the keys. Where series is required, the names must be known in advance; the ones the examples on this site use are listed above.

Timeseries catalog

Which column is the series key of every model (seriesKey: true).

Tabular catalog

Which columns are primaryKey and identifier on every lookup model.

Tabular vs timeseries

How the two model kinds compose.

Responses

What entity and points look like once you have the key.