Metadata
Assets
GET
https://api.glassnode.com/v1/metadata/assets
Lists all assets and relevant metadata.
The base request returns the complete list of all known assets. With the query parameter, filter
, the data can also be queried via Common Expression Language (CEL). See Assets Metadata Usage for usage examples and cel.dev for more details.
Schema
Asset
id
string
Glassnode ID -- a unique string-based identifier used to specify assets; typically matches with an asset's symbol
external_ids
External IDs
references to external IDs of third party entities such as CoinMarketCap, Coingecko or CCData
symbol
string
asset symbol -- used in Studio when referencing assets
name
string
asset name
asset_type
string
asset type -- one of: BLOCKCHAIN or TOKEN
blockchains
List[Blockchain]
Blockchain
blockchain
string
unique blockchain identifier
address
string
contract address for the asset on the given blockchain
decimals
integer
number of decimals places in the blockchain
on_chain_support
boolean
whether Glassnode offers on-chain metrics for the given blockchain
External IDs
ccdata
string
CCData ID
coinmarketcap
string
CoinMarketCap ID
coingecko
string
CoinGecko ID
Query Parameters
filter
string
CEL (Common Expression Language) compliant filter
Assets Metadata Usage
Examples
Filter asset by id
GET
https://api.glassnode.com/v1/metadata/assets?filter=asset.id=='USDT'
Filter asset with CoinGecko id
GET
https://api.glassnode.com/v1/metadata/assets?filter=asset.external_ids.coingecko=='tether'
Filter assets listed on ETH blockchain
GET
https://api.glassnode.com/v1/metadata/assets?filter=asset.blockchains.exists(b,b.blockchain=='ETH')
Find all supported assets
GET
https://api.glassnode.com/v1/metadata/assets?filter=asset.blockchains.exists(b,b.on_chain_support==true)
Metrics
GET
https://api.glassnode.com/v1/metadata/metrics
Lists all available metric paths. This should be used as the base list which can then be used to retrieve metadata from the detail view Metric Metadata.
Note:
the paths only include the metric portion of the path, and not the full path containing /v1/metrics
.
Metric
GET
https://api.glassnode.com/v1/metadata/metric
Retrieves metadata describing the available parameters and potential drill-down options for a metric.
The base request, where only path
is queried, returns the union of all possible parameters and their values.
If the response contains next_parameter
, this indicates that query parameters are distinct across next_parameter
values. If not present in the base response, all request parameters have the same supported set of values.
Once next_parameter
is no longer present, no further narrowing of values is possible and the response represents the set of valid parameters and values for the query.
See Metric Metadata Usage for a complete example.
Schema
path
string
metric path
always
parameters
Dict[string, List[string]]
list of all allowed parameters and their values
always
next_parameter
string
should the metric possess a hierarchy by which the valid parameters change, this key-value pair denotes the next available parameter which can be queried
only present in the response when a drill-down is available
queried
Dict[string, string]
the query which was processed by the server; extraneous values will not be queried
always
modified
int
the last unix timestamp that the metadata was updated in UTC
refs
Dict[string, string]
links to the metric in studio and its documentation
Query Parameters
path*
string
metric path: /addresses/count
a
string
asset id: BTC
Metric Metadata Usage
Request metadata for metric:
GET
https://api.glassnode.com/v1/metadata/metric?path=/distribution/balance_exchanges
Add the value of next_parameter
to the query with a value from the response to refine the query further. Continue this process until next_parameter
is no longer present in the response.
GET
https://api.glassnode.com/v1/metadata/metric?path=/distribution/balance_exchanges&a=BTC
The result displays the set of valid parameters and their values given the query:
Last updated