GET
/
v1
/
metrics
/
{identifier}
Get Metric By Identifier
curl --request GET \
  --url https://api.blockworks.com/v1/metrics/{identifier} \
  --header 'x-api-key: <api-key>'
{
  "Bitcoin": {
    "date": "2000-12-31",
    "value": 1
  },
  "Ethereum": {
    "date": "2000-12-31",
    "value": 2
  }
}

​
Overview

The GET /v1/metrics/{identifier} endpoint returns a time series for a single metric across one or more projects. Metrics are curated, aggregated datasets (usually daily) such as network revenue, token supply, or DEX volume. Each metric has a stable identifier and consistent schema, with methodology documented in the Metrics Catalog.

​
Basic Example

curl -H "x-api-key: YOUR_API_KEY" \\
  "https://api.blockworks.com/v1/metrics/rev-usd?project=ethereum"

​
Multiple Projects Example

If supported, request multiple projects in a single call by separating them with commas: 
curl -H "x-api-key: YOUR_API_KEY" \\
  "https://api.blockworks.com/v1/metrics/rev-usd?project=ethereum,optimism,arbitrum"

​
Response Structure

Returns a JSON object where each key is a project identifier, and its value is an array of date/value pairs. Ethereum REV in USD example: 
{
  "ethereum": [
    { "date": "2015-08-07", "value": 0 },
    { "date": "2015-08-08", "value": 0 },
    ...
    { "date": "2025-08-06", "value": 948090.6293758566 },
    { "date": "2025-08-07", "value": 1175055.4507596379 },
    { "date": "2025-08-08", "value": 1370617.1360337874 }
  ]
}

​
Response Fields

FieldTypeDescription
<project>arrayTop-level key matching the project slug
datestringISO-8601 date for the data point
valuenumberMetric value for that date in the requested unit

​
Configuration

​
Path Parameters

ParameterTypeDescriptionRequired
identifierstringMetric identifierYes
Use the identifier from the List Metrics endpoint to specify which metric to retrieve.

​
Query Parameters

ParameterTypeDescriptionDefault
projectstringProject identifier (slug)Required
start_datestringStart date (YYYY-MM-DD)30 days ago
end_datestringEnd date (YYYY-MM-DD)Today

​
Error Example

{
  "error": {
    "type": "not_found",
    "message": "Metric identifier 'foo-bar' not found",
    "request_id": "abcd1234"
  }
}
For details on valid metric identifiers and project slugs, see List Metrics and Projects Supported.

Authorizations

​
x-api-key
string
header
required

Path Parameters

​
identifier
string
required

Query Parameters

​
project
any[]
required
Minimum length: 1
Example:

"Bitcoin,Ethereum"

Response

200
application/json

The response is of type object.