Deposits

ETF Deposits

Definition

The sum of assets sent to an ETF that interval.

Name

MetricID

Unit

Interval

ARK Invest Deposits (native units)

FlowInARKNtv

Native units

1 day

ARK Invest Deposits (USD)

FlowInARKUSD

USD

1 day

BlackRock Deposits (native units)

FlowInBLKNtv

Native units

1 day

BlackRock Deposits (USD)

FlowInBLKUSD

USD

1 day

Bitwise Deposits (native units)

FlowInBWSNtv

Native units

1 day

Bitwise Deposits (USD)

FlowInBWSUSD

USD

1 day

Exchange Traded Fund deposits, Including EtoE (native units)

FlowInEtfInclNtv

Native units

1 day

Exchange Traded Fund deposits, Including EtoE (USD)

FlowInEtfInclUSD

USD

1 day

Exchange Traded Fund Deposits (native units)

FlowInEtfNtv

Native units

1 day

Exchange Traded Fund Deposits (USD)

FlowInEtfUSD

USD

1 day

Grayscale Deposits (native units)

FlowInGSCNtv

Native units

1 day

Grayscale Deposits (USD)

FlowInGSCUSD

USD

1 day

Invesco Deposits (native units)

FlowInINVNtv

Native units

1 day

Invesco Deposits (USD)

FlowInINVUSD

USD

1 day

Franklin Templeton Deposits (native units)

FlowInTMPNtv

Native units

1 day

Franklin Templeton Deposits (USD)

FlowInTMPUSD

USD

1 day

VanEck Deposits (native units)

FlowInVANNtv

Native units

1 day

VanEck Deposits (USD)

FlowInVANUSD

USD

1 day

Valkyrie Deposits (native units)

FlowInVLKNtv

Native units

1 day

Valkyrie Deposits (USD)

FlowInVLKUSD

USD

1 day

WisdomTree Deposits (native units)

FlowInWDTNtv

Native units

1 day

WisdomTree Deposits (USD)

FlowInWDTUSD

USD

1 day

Details

Native units are considered as sent to an ETF if they are sent to an address we identify as being owned by an ETF.
USD flows are computed as FlowIn{ETF}Ntv * PriceUSD

Asset-Specific Details

For Bitcoin, this metric excludes the effect of change outputs:
- If a transaction sends 90 BTC to exchange A but also withdraws 50 BTC from it, the flow is +40 BTC, not +90 BTC and -50 BTC.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

ETF Deposit Count

Definition

The sum count of transfers to any address belonging to an ETF in that interval. If the sender address also belongs to an ETF, the transfer is not counted.

Name

MetricID

Unit

Interval

ARK Invest Deposit Count

FlowTfrInARKCnt

Deposits

1 day

BlackRock Deposit Count

FlowTfrInBLKCnt

Deposits

1 day

Bitwise Deposit Count

FlowTfrInBWSCnt

Deposits

1 day

Grayscale Deposit Count

FlowTfrInGSCCnt

Deposits

1 day

Invesco Deposit Count

FlowTfrInINVCnt

Deposits

1 day

Franklin Templeton Deposit Count

FlowTfrInTMPCnt

Deposits

1 day

VanEck Deposit Count

FlowTfrInVANCnt

Deposits

1 day

Valkyrie Deposit Count

FlowTfrInVLKCnt

Deposits

1 day

WisdomTree Deposit Count

FlowTfrInWDTCnt

Deposits

1 day

Exchange Traded Fund Deposits Count

FlowTfrToEtfCnt

Deposits

1 day

Exchange Traded Fund Deposits Count, incl EtoE

FlowTfrToEtfInclCnt

Deposits

1 day

Details

Coinbase (i.e., miner reward) transactions are not counted.

Asset-Specific Details

For UTXO-based protocols, this metric does not count change outputs:
- If the input addresses belong to a given ETF, then the outputs belonging to the same ETF are not counted as transfers to that ETF

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

API Endpoints

ETF Deposits metrics can be accessed using these endpoints:

timeseries/asset-metrics

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

Asset metrics

get

Returns requested metrics for specified assets. 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. Supported output formats are json (default) and csv, use format query parameter to override it. To fetch the next page of results use next_page_url JSON response field or x-next-page-url CSV HTTP header if present. If multiple metrics are requested in the same time the strict policy for partially available metrics among requested ones is applied:

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.
`null` value of the metric means "no data in the database" while some other requested metrics have data.

Authorizations

Query parameters

assetsstring[]Required

Comma separated list of assets. Use the /catalog-all-v2/asset-metrics 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. Information on all available metrics can be found on page https://coverage.coinmetrics.io/asset-metrics-v2. Use the /catalog-all-v2/asset-metrics endpoint for the full list of supported metrics per asset.

Example: ["AdrActCnt","BlkHgt"]

frequencystringOptional

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

Default: 1dExample: 1b

statusstring · enumOptional

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

Default: allPossible values:

start_timestringOptional

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. Mutually exclusive with start_height and start_hash. 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_timestringOptional

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. Mutually exclusive with end_height and end_hash. 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.

start_heightinteger · int64Optional

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

end_heightinteger · int64Optional

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

start_hashstringOptional

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

end_hashstringOptional

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

start_inclusivebooleanOptional

Inclusive or exclusive corresponding start_* parameters.

Default: true

end_inclusivebooleanOptional

Inclusive or exclusive corresponding end_* parameters.

Default: true

min_confirmationsinteger · int32 · max: 99Optional

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).

timezonestringOptional

Timezone 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.

Default: UTCExample: America/New_York

page_sizeinteger · int32 · min: 1 · max: 10000Optional

Number 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.

Default: 100

paging_fromstring · enumOptional

Where 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.

Default: endPossible values:

sortstring · enumOptional

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. Sorting by time is useful if you request metrics for a set of assets.

Default: assetPossible values:

limit_per_assetinteger · int32Optional

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.

prettybooleanOptional

Human-readable formatting of JSON responses.

Default: false

formatstring · enumOptional

Format of the response.

Default: jsonPossible values:

null_as_zerobooleanOptional

Nulls are represented as zeros in the response.

Default: false

next_page_tokenstringOptional

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.

ignore_forbidden_errorsbooleanOptional

Ignore "forbidden" errors for the items you currently don't have access to.

Default: false

ignore_unsupported_errorsbooleanOptional

Ignore "unsupported" errors for not currently supported by Coin Metrics items.

Default: false

Responses

200

Time series of metrics for an asset.

400

Asset not found.

application/json

401

Requested resource requires authorization.

application/json

403

Requested resource is not available with supplied credentials.

application/json

414

Provided URI is too long. It must not be greater than 10000 symbols.

{
  "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"
}

curl --compressed "https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=FlowInARKNtv&assets=btc&pretty=true&api_key=<your_key>"

import requests
response = requests.get('https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=FlowInARKNtv&assets=btc&pretty=true&api_key=<your_key>').json()
print(response)

from coinmetrics.api_client import CoinMetricsClient

api_key = "<API_KEY>"
client = CoinMetricsClient(api_key)

print(
    client.get_asset_metrics(
        metrics="FlowInARKNtv", 
        assets="btc",
    ).to_dataframe()
)

PreviousExchange Traded Fund NextExchange Traded Fund Supply

Last updated 8 days ago

Was this helpful?

Contents

ETF Deposits

Definition

Details

Asset-Specific Details

Availability for Assets

ETF Deposit Count

Definition

Details

Asset-Specific Details

Availability for Assets

API Endpoints

Asset metrics