Protocol metrics
Coin Metrics API key can be specified as ?api_key= query parameter.
Comma separated list of protocols like aave_v3 or morpho_blue.
Comma separated list of protocol chains like ethereum or base.
Comma separated list of protocol markets like core-weth or steakusdc.
Frequency of the protocol metrics. Supported values are 1d, 1m.
Comma separated list of protocol metrics like supply_apy.
Start of the time interval.
This field refers to the time field in the response.
Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z, 2006-01-20T00:00:00.000Z, 2006-01-20T00:00:00.123456Z, 2006-01-20T00:00:00.123456789Z, 2006-01-20, 20060120.
Inclusive by default.
UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.
If start_time is omitted, response will include time series from the earliest time available.
End of the time interval.
This field refers to the time field in the response.
Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z, 2006-01-20T00:00:00.000Z, 2006-01-20T00:00:00.123456Z, 2006-01-20T00:00:00.123456789Z, 2006-01-20, 20060120.
Inclusive by default.
UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.
If end_time is omitted, response will include time series up to the latest time available.
Inclusive or exclusive corresponding start_* parameters.
trueInclusive or exclusive corresponding end_* parameters.
trueTimezone name for start_time and end_time timestamps.
This parameter does not modify the output times, which are always UTC.
Format is defined by TZ database.
UTCExample: America/New_YorkNumber of items per single page of results.
The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.
100Where does the first page start, at the start of the interval or at the end.
The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.
startPossible values: Token for receiving the results from the next page of a query.
Should not be used directly. To iterate through pages just use next_page_url response field.
Format of the response. Supported values are json, json_stream.
jsonHuman-readable formatting of JSON responses.
falseTime series of protocol metrics.
Time series of protocol metrics.
Protocol metric value.
Token of the next page results for a given request.
URL of the next page results for a given request.
Protocol not found.
Requested resource requires authorization.
Provided URI is too long. It must not be greater than 10000 symbols.
Last updated
Was this helpful?