Reported Volume

The reported volume aggregated across all exchanges in CM's coverage universe. These metrics do not use the Trusted Exchange Framework to filter for the most accurate and trustworthy crypto exchanges. See Trusted Volume for more details on the distinction for trustworthy exchanges.

Contents

• Spot Volume

• Perpetual Future

• Non-Perpetual Future

• Future Coin-Margined

• Tether Coin-Margined

Reported Spot Volume

Definition

The sum of all reported volume from the spot markets in Coin Metrics' coverage in units of U.S. dollars.

Name	MetricID	Unit	Interval
Reported Spot Volume	volume_reported_spot_usd_1d	USD	1d
Reported Spot Volume, 1 Hour	volume_reported_spot_usd_1h	USD	1h

Details

Our reported volume metric is an aggregation of the reported volume from all exchanges in CM's coverage universe. Covered exchanges can be found here.

Chart

Spot volume and futures volume

Examples

A sample of the daily reported spot volume for Bitcoin is shown below:

assets	time	volume_reported_spot_usd_1d
btc	2021-07-25 00:00:00	7790004055.86305
btc	2021-07-26 00:00:00	27380811113.0087
btc	2021-07-27 00:00:00	16167140594.9998
btc	2021-07-28 00:00:00	19318207388.4525

• asset. The IDs of the asset.

• time. The reference rate time in ISO 8601 date-time format.

• reported_trusted_spot_usd_1d. The reported volume value in units of U.S. dollars.

Release History

• Release Version. Market Data Feed 2.4 (August 2021)

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Reported Future Volume

Definition

The sum of all reported future volume from the spot markets in Coin Metrics' coverage in units of U.S. dollars.

Name	MetricID	Unit	Interval
Reported Future Volume	volume_reported_future_usd_1d	USD	1d
Reported Future Volume, 1 Hour	volume_reported_future_usd_1h	USD	1h

Details

Our reported future volume metric is an aggregation of the reported future volume from all futures exchanges in CM's coverage universe. Covered exchanges can be found here.

Chart

Spot volume and futures volume

Release History

• Release Version. Market Data Feed 2.4 (August 2021)

See Also

• Futures Contract Specifications

Reported Perpetual Future Volume

Definition

The sum of all reported volume from perpetual futures markets in units of U.S. dollars.

Name	MetricID	Unit	Interval
Reported Perpetual Future Volume	volume_reported_future_perpetual_usd_1d	USD	1d
Reported Perpetual Future Volume, 1 Hour	volume_reported_future_perpetual_usd_1h	USD	1h

Details

Our perpetual future volume metric is an aggregation of the reported perpetual futures volume from all futures exchanges in CM's coverage universe. Covered exchanges can be found here.

Release History

• Release Version. Market Data Feed 2.4 (August 2021)

See Also

• Futures Contract Specifications

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Reported Non-Perpetual Future Volume

Definition

The sum of all reported volume from non-perpetual futures markets in units of U.S. dollars.

Name	MetricID	Unit	Interval
Reported Non-Perpetual Future Volume	volume_reported_future_nonperpetual_usd_1d	USD	1d
Reported Non-Perpetual Future Volume, 1 Hour	volume_reported_future_nonperpetual_usd_1h	USD	1h

Details

Our non-perpetual future volume metric is an aggregation of the reported non-perpetual futures volume from all futures exchanges in CM's coverage universe. Covered exchanges can be found here.

Release History

• Release Version. Market Data Feed 2.4 (August 2021)

See Also

• Futures Contract Specifications

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Reported Coin-Margined Future Volume

Definition

The sum of all reported volume from futures markets where the margin asset is equivalent to the underlying base asset in units of U.S. dollars.

Name	MetricID	Unit	Interval
Reported Coin-Margined Future Volume	volume_reported_future_coin_margined_usd_1d	USD	1d
Reported Coin-Margined Future Volume, 1 Hour	volume_reported_future_coin_margined_usd_1h	USD	1h

Details

Our reported coin-margined future volume metric is an aggregation of the reported coin-margined future volume from all futures exchanges in CM's coverage universe. Covered exchanges can be found here.

Reported Tether-Margined Future Volume

Definition

The sum of all reported volume from futures markets where the margin asset is Tether in units of U.S. dollars.

Name	MetricID	Unit	Interval
Reported Tether-Margined Future Volume	volume_reported_tether_margined_usd_1d	USD	1d
Reported Tether-Margined Future Volume, 1 Hour	volume_reported_tether_margined_usd_1h	USD	1h

Details

Our reported Tether-margined future volume metric is an aggregation of the reported Tether-margined future volume from all futures exchanges in CM's coverage universe. Covered exchanges can be found here.

Release History

• Release Version. Market Data Feed 2.4 (August 2021)

See Also

• Futures Contract Specifications

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

API Endpoints

All reported volume metrics can be queried using the following endpoints:

• /timeseries/asset-metrics

• /timeseries/exchange-metrics

• /timeseries/exchange-asset-metrics

• /timeseries/pair-metrics

and by passing in volume_reported_* metric ID's in the the metrics parameter.

Asset metrics

Returns requested metrics for specified assets.<br/><br/> Results for block by block metrics (1b frequency) are ordered by tuple (asset, height, block_hash), all other metrics are ordered by tuple (asset, time). You can change the sorting using sort query parameter.<br/><br/> Supported output formats are json (default) and csv, use format query parameter to override it.<br/> To fetch the next page of results use next_page_url JSON response field or x-next-page-url CSV HTTP header if present.<br/><br/> If multiple metrics are requested in the same time the strict policy for partially available metrics among requested ones is applied: <ul>

<li>missing metric name in the JSON response means that the metric is "not a supported metric" for the asset and frequency while some other requested metrics are supported.</li> <li>`null` value of the metric means "no data in the database" while some other requested metrics have data.</li> </ul>

get

/timeseries/asset-metrics

Authorizations

Query parameters

assetsstring[]required

Comma separated list of assets.<br/> Use the /catalog-all/assets endpoint for the full list of supported assets or specify asterisk (*) in order to get metrics for all supported assets.

metricsstring[]required

Comma separated metrics to request time series data for.<br/> Information on all available metrics can be found on page https://docs.coinmetrics.io/info/metrics.<br/> Use the /catalog-all/metrics or /catalog-all/assets endpoint for the full list of supported metrics per asset.

Example: ["AdrActCnt","BlkHgt"]

frequencystring · default: 1d

Frequency of the metrics. Supported values are 1b (block by block), 1s (one second), 1m (one minute), 10m (ten minutes), 1h (one hour), 1d (one day), 1d-ny-close (one day at New York close time). Please refer to the /catalog/metrics endpoint for the full list.<br/> Use the /catalog-all/assets endpoint for the full list of supported frequencies per asset-metric pair.

Example: 1b

statusstring · enum · default: all

Which metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics endpoint.

Options: all, flash, reviewed, revised

start_timestring

Start of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default. Mutually exclusive with start_height and start_hash.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If start_time is omitted, response will include time series from the earliest time available.

end_timestring

End of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default. Mutually exclusive with end_height and end_hash.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If end_time is omitted, response will include time series up to the latest time available.

start_heightinteger · int64

The start height indicates the beginning block height for the set of data that are returned.<br/> Inclusive by default. Mutually exclusive with start_time and start_hash.

end_heightinteger · int64

The end height indicates the ending block height for the set of data that are returned.<br/> Inclusive by default. Mutually exclusive with end_time and end_hash.<br/> This parameter is disabled for Community users.

start_hashstring

The start hash indicates the beginning block height for the set of data that are returned.<br/> Inclusive by default. Mutually exclusive with start_time and start_height.

end_hashstring

The end hash indicates the ending block height for the set of data that are returned.<br/> Inclusive by default. Mutually exclusive with end_time and end_height.

start_inclusiveboolean · default: true

Inclusive or exclusive corresponding start_* parameters.

end_inclusiveboolean · default: true

Inclusive or exclusive corresponding end_* parameters.

min_confirmationsinteger · int32 · max: 99

Specifies how many blocks behind the chain tip block by block metrics (1b frequency) are based on. Default for btc is 2 and 99 for eth. For example, a min_confirmations of 0 means metrics are being calculated for the block at the tip of the chain (the latest block received by our node) whereas a min_confirmations of 6 means that metrics are being applied to the block that is 6 blocks behind the chain tip (i.e., the 7th block if the chain tip is block 1).

timezonestring · default: UTC

Timezone name for start_time and end_time timestamps.<br/> This parameter does not modify the output times, which are always UTC.<br/> Format is defined by TZ database.

Example: America/New_York

page_sizeinteger · int32 · min: 1 · max: 10000 · default: 100

Number of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.

paging_fromstring · enum · default: end

Where does the first page start, at the start of the interval or at the end.

Options: start, end

sortstring · enum · default: asset

How results will be sorted. Metrics with 1b frequency are sorted by (asset, height, block_hash) tuples by default. Metrics with other frequencies are sorted by (asset, time) by default. If you want to sort 1d metrics by (time, asset) you should choose time as value for the sort parameter.<br/> Sorting by time is useful if you request metrics for a set of assets.

Options: asset, height, time

limit_per_assetinteger · int32

How many entries per asset result should contain. For example, this combination of parameters assets=btc,eth&metrics=ReferenceRate&limit_per_asset=1 returns the latest ReferenceRate values for btc and eth.

prettyboolean · default: false

Human-readable formatting of JSON responses.

formatstring · enum · default: json

Format of the response.

Options: json, csv

null_as_zeroboolean · default: false

Nulls are represented as zeros in the response.

next_page_tokenstring

Token for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url response field.

ignore_forbidden_errorsboolean · default: false

Ignore HTTP 403 Forbidden errors

ignore_unsupported_errorsboolean · default: false

Ignore errors for unsupported assets, metrics or frequencies.

Responses

application/jsontext/csv

application/json

application/json

application/json

200

400

401

403

414

200

application/json

text/csv

application/json

Example of a message with daily metrics.

Example of a message with block by block metrics.

Example of a message with 1s metrics.

Example of a message with daily metrics.

{
  "data": [
    {
      "asset": "btc",
      "time": "2020-02-29T00:00:00.000000000Z",
      "PriceUSD": "8582.09029964933",
      "SplyBMXNtv": "283220.10827406",
      "SplyBMXNtv-status": "reviewed",
      "SplyBMXNtv-status-time": "2020-03-01T09:59:13.847251000Z"
    },
    {
      "asset": "btc",
      "time": "2020-03-01T00:00:00.000000000Z",
      "PriceUSD": "8541.77389392169",
      "SplyBMXNtv": "284691.32323907",
      "SplyBMXNtv-status": "reviewed",
      "SplyBMXNtv-status-time": "2020-03-02T14:00:02.622168000Z"
    }
  ],
  "next_page_token": "0.MjAyMC0wNi0wN1QwMDowMDowMFo,MjAyMC0wNi0wN1QwMDowMDowMFo",
  "next_page_url": "https://api.coinmetrics.io/v4/timeseries/asset-metrics?api_key=<your_key>&pretty=true&assets=btc&metrics=SplyBMXNtv,PriceUSD&page_size=2&next_page_token=0.MjAyMC0wNi0wN1QwMDowMDowMFo,MjAyMC0wNi0wN1QwMDowMDowMFo"
}

Time series of metrics for an asset.

Exchange metrics

Returns metrics for specified exchanges.<br/> Results are ordered by tuple (exchange, time).<br/> To fetch the next page of results use next_page_url JSON response field.<br/>

get

/timeseries/exchange-metrics

Authorizations

Query parameters

exchangesstring[]required

Comma separated list of exchange names or asterisk (*) for all supported exchanges.

Example: {"summary":"the list of exchanges","value":"coinbase,binance,etc"}

metricsstring[]required

Comma separated metrics to request time series data for.<br/> Information on all available metrics can be found on page https://docs.coinmetrics.io/info/pair_metrics.<br/> Use the /catalog-all/exchange endpoint for the full list of supported metrics per exchange.

Example: ["open_interest_reported_future_usd","volume_reported_spot_usd_1d"]

frequencystring · default: 1d

Frequency of the exchange metrics. Supported values are 1h, 1d.

start_timestring

Start of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If start_time is omitted, response will include time series from the earliest time available.

end_timestring

End of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If end_time is omitted, response will include time series up to the latest time available.

start_inclusiveboolean · default: true

Inclusive or exclusive corresponding start_* parameters.

end_inclusiveboolean · default: true

Inclusive or exclusive corresponding end_* parameters.

timezonestring · default: UTC

Timezone name for start_time and end_time timestamps.<br/> This parameter does not modify the output times, which are always UTC.<br/> Format is defined by TZ database.

Example: America/New_York

page_sizeinteger · int32 · min: 1 · max: 10000 · default: 100

Number of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.

paging_fromstring · enum · default: end

Where does the first page start, at the start of the interval or at the end.

Options: start, end

sortstring · enum · default: exchange

How results will be sorted. Metrics are sorted by (exchange, time) by default. If you want to sort 1d metrics by (time, exchange) you should choose time as value for the sort parameter.<br/> Sorting by time is useful if you request metrics for a set of exchanges.

Options: exchange, time

limit_per_exchangeinteger · int32

How many entries per institution result should contain. For example, this combination of parameters exchanges=binance,coinbase&metrics=volume_trusted_spot_usd_1h&limit_per_exchange=1 returns the latest volume_trusted_spot_usd_1h values for binance and coinbase.

prettyboolean · default: false

Human-readable formatting of JSON responses.

formatstring · enum · default: json

Format of the response.

Options: json, csv

next_page_tokenstring

Token for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url response field.

Responses

application/json

application/json

application/json

application/json

200

400

401

403

414

200

{
  "data": [
    {
      "exchange": "binance",
      "time": "2022-01-01T00:00:00.000000000Z",
      "volume_reported_spot_usd_1d": "8988114373.91716"
    },
    {
      "exchange": "binance",
      "time": "2022-01-02T00:00:00.000000000Z",
      "volume_reported_spot_usd_1d": "9686610104.12659"
    },
    {
      "exchange": "binance",
      "time": "2022-01-03T00:00:00.000000000Z",
      "volume_reported_spot_usd_1d": "13513437237.6032"
    },
    {
      "exchange": "binance",
      "time": "2022-01-04T00:00:00.000000000Z",
      "volume_reported_spot_usd_1d": "15006844836.1782"
    }
  ]
}

Time series of exchange metrics.

Exchange-asset metrics

Returns metrics for specified exchange-asset.<br/> Results are ordered by tuple (exchange_asset, time).<br/> To fetch the next page of results use next_page_url JSON response field.<br/>

get

/timeseries/exchange-asset-metrics

Authorizations

Query parameters

exchange_assetsstring[]required

Comma separated list of exchange-asset pairs or patterns like exchange-* or *-asset.

metricsstring[]required

Comma separated metrics to request time series data for.<br/> Information on all available metrics can be found on page https://docs.coinmetrics.io/info/pair_metrics.<br/> Use the /catalog-all/exchange-assets endpoint for the full list of supported metrics per exchange-asset combination.

Example: ["open_interest_reported_future_usd","volume_reported_spot_usd_1d"]

frequencystring · default: 1d

Frequency of the exchange-asset metrics. Supported values are 5m, 1h, 1d.

start_timestring

Start of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If start_time is omitted, response will include time series from the earliest time available.

end_timestring

End of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If end_time is omitted, response will include time series up to the latest time available.

start_inclusiveboolean · default: true

Inclusive or exclusive corresponding start_* parameters.

end_inclusiveboolean · default: true

Inclusive or exclusive corresponding end_* parameters.

timezonestring · default: UTC

Timezone name for start_time and end_time timestamps.<br/> This parameter does not modify the output times, which are always UTC.<br/> Format is defined by TZ database.

Example: America/New_York

page_sizeinteger · int32 · min: 1 · max: 10000 · default: 100

Number of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.

paging_fromstring · enum · default: end

Where does the first page start, at the start of the interval or at the end.

Options: start, end

sortstring · enum · default: exchange_asset

How results will be sorted. Metrics are sorted by (exchange_asset, time) by default. If you want to sort 1d metrics by (time, exchange_asset) you should choose time as value for the sort parameter.<br/> Sorting by time is useful if you request metrics for a set of exchange-assets.

Options: exchange_asset, time

limit_per_exchange_assetinteger · int32

How many entries per exchange_asset result should contain. For example, this combination of parameters exchange_assets=binance-btc,coinbase-eth&metrics=volume_trusted_spot_usd_1h&limit_per_exchange_asset=1 returns the latest volume_trusted_spot_usd_1h values for binance-btc and coinbase-eth.

prettyboolean · default: false

Human-readable formatting of JSON responses.

formatstring · enum · default: json

Format of the response.

Options: json, csv

next_page_tokenstring

Token for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url response field.

Responses

application/json

application/json

application/json

application/json

200

400

401

403

414

200

{
  "data": [
    {
      "exchange_asset": "binance-btc",
      "time": "2021-10-04T00:00:00.000000000Z",
      "open_interest_reported_future_usd": "3469621227.0258"
    },
    {
      "exchange_asset": "binance-btc",
      "time": "2021-10-05T00:00:00.000000000Z",
      "open_interest_reported_future_usd": "3562791590.02995"
    },
    {
      "exchange_asset": "binance-btc",
      "time": "2021-10-06T00:00:00.000000000Z",
      "open_interest_reported_future_usd": "3970248573.60142"
    },
    {
      "exchange_asset": "binance-btc",
      "time": "2021-10-07T00:00:00.000000000Z",
      "open_interest_reported_future_usd": "4110308192.96416"
    }
  ]
}

Time series of exchange-asset metrics.

Pair metrics

Returns metrics for specified asset pairs.<br/> Results are ordered by tuple (pair, time).<br/> To fetch the next page of results use next_page_url JSON response field.<br/>

get

/timeseries/pair-metrics

Authorizations

Query parameters

pairsstring[]required

Comma separated list of asset pairs.<br/> Use the /catalog-all/pairs endpoint for the full list of supported asset pairs.

metricsstring[]required

Comma separated metrics to request time series data for.<br/> Information on all available metrics can be found on page https://docs.coinmetrics.io/info/pair_metrics.<br/> Use the /catalog-all/pairs endpoint for the full list of supported metrics per pair.

Example: ["volume_trusted_spot_usd_1h","volume_trusted_spot_usd_1d"]

frequencystring · default: 1d

Frequency of the pair metrics. Supported values are 1h, 1d.

start_timestring

Start of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If start_time is omitted, response will include time series from the earliest time available.

end_timestring

End of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If end_time is omitted, response will include time series up to the latest time available.

start_inclusiveboolean · default: true

Inclusive or exclusive corresponding start_* parameters.

end_inclusiveboolean · default: true

Inclusive or exclusive corresponding end_* parameters.

timezonestring · default: UTC

Timezone name for start_time and end_time timestamps.<br/> This parameter does not modify the output times, which are always UTC.<br/> Format is defined by TZ database.

Example: America/New_York

page_sizeinteger · int32 · min: 1 · max: 10000 · default: 100

Number of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.

paging_fromstring · enum · default: end

Where does the first page start, at the start of the interval or at the end.

Options: start, end

sortstring · enum · default: pair

How results will be sorted. Metrics are sorted by (pair, time) by default. If you want to sort 1d metrics by (time, pair) you should choose time as value for the sort parameter.<br/> Sorting by time is useful if you request metrics for a set of asset pairs.

Options: pair, time

limit_per_pairinteger · int32

How many entries per pair result should contain. For example, this combination of parameters pair=btc-usd,eth-usd&metrics=volume_trusted_spot_usd_1h&limit_per_pair=1 returns the latest volume_trusted_spot_usd_1h values for btc-usd and eth-usd.

prettyboolean · default: false

Human-readable formatting of JSON responses.

formatstring · enum · default: json

Format of the response.

Options: json, csv

next_page_tokenstring

Token for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url response field.

Responses

application/json

application/json

application/json

application/json

200

400

401

403

414

200

{
  "data": [
    {
      "pair": "btc-usd",
      "time": "2020-09-28T00:00:00.000000000Z",
      "volume_trusted_spot_usd_1d": "317000178.776577"
    },
    {
      "pair": "btc-usd",
      "time": "2020-09-29T00:00:00.000000000Z",
      "volume_trusted_spot_usd_1d": "246153685.485477"
    },
    {
      "pair": "btc-usd",
      "time": "2020-09-30T00:00:00.000000000Z",
      "volume_trusted_spot_usd_1d": "217972373.240482"
    },
    {
      "pair": "btc-usd",
      "time": "2020-10-01T00:00:00.000000000Z",
      "volume_trusted_spot_usd_1d": "492203699.871197"
    }
  ]
}

Time series of pair metrics.