Liquidation Metrics
The reported liquidation metrics are a sum of all reported volume in native units or U.S. Dollars of buy or sell orders that were used to close short positions under liquidation for a specific market in our coverage universe.
Metrics
Reported Liquidation Buy Orders (Units), 5 Min
Native Units
5m
Reported Liquidation Buy Orders (Units), 1 Hour
Native Units
1h
Reported Liquidation Buy Orders (Units), 1 Day
Native Units
1d
Reported Liquidation Sell Orders (Units), 5 Min
Native Units
5m
Reported Liquidation Sell Orders (Units), 1 Hour
Native Units
1h
Reported Liquidation Sell Orders (Units), 1 Day
Native Units
1d
API Endpoints
Liquidation metrics can be accessed using these endpoints:
timeseries/exchange-metrics
timeseries/exchange-asset-metrics
timeseries/pair-metrics
and by passing in the liquidation_reported_*
metrics in the metrics
parameter.
Returns metrics for specified exchanges. Results are ordered by tuple (exchange, time)
. To fetch the next page of results use next_page_url
JSON response field.
Comma separated list of exchange names or asterisk (*) for all supported exchanges.
{"summary":"the list of exchanges","value":"coinbase,binance,etc"}
Comma separated metrics to request time series data for. Information on all available metrics can be found on page https://coverage.coinmetrics.io/exchange-metrics-v2. Use the /catalog-all/exchange endpoint for the full list of supported metrics per exchange.
["open_interest_reported_future_usd","volume_reported_spot_usd_1d"]
Frequency of the exchange metrics. Supported values are 1h
, 1d
.
1d
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.
true
Inclusive or exclusive corresponding end_*
parameters.
true
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.
UTC
Example: America/New_York
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
.
100
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
.
end
Possible values: 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. Sorting by time
is useful if you request metrics for a set of exchanges.
exchange
Possible values: 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
.
Human-readable formatting of JSON responses.
false
Format of the response.
json
Possible 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.
Returns metrics for specified exchange-asset. Results are ordered by tuple (exchange_asset, time)
. To fetch the next page of results use next_page_url
JSON response field.
Comma separated list of exchange-asset pairs or patterns like exchange-*
or *-asset
.
Comma separated metrics to request time series data for. Information on all available metrics can be found on page https://coverage.coinmetrics.io/exchange-asset-metrics-v2. Use the /catalog-all/exchange-assets endpoint for the full list of supported metrics per exchange-asset combination.
["open_interest_reported_future_usd","volume_reported_spot_usd_1d"]
Frequency of the exchange-asset metrics. Supported values are 5m
, 1h
, 1d
.
1d
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.
true
Inclusive or exclusive corresponding end_*
parameters.
true
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.
UTC
Example: America/New_York
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
.
100
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
.
end
Possible values: 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. Sorting by time
is useful if you request metrics for a set of exchange-assets.
exchange_asset
Possible values: 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
.
Human-readable formatting of JSON responses.
false
Format of the response.
json
Possible 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.
Returns metrics for specified asset pairs. Results are ordered by tuple (pair, time)
. To fetch the next page of results use next_page_url
JSON response field.
Comma separated list of asset pairs or patterns like btc-*
, or *-btc
. Use the /catalog-all/pairs endpoint for the full list of supported asset pairs.
Comma separated metrics to request time series data for. Information on all available metrics can be found on page https://coverage.coinmetrics.io/pair-metrics-v2. Use the /catalog-all/pairs endpoint for the full list of supported metrics per pair.
["volume_trusted_spot_usd_1h","volume_trusted_spot_usd_1d"]
Frequency of the pair metrics. Supported values are 1h
, 1d
.
1d
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.
true
Inclusive or exclusive corresponding end_*
parameters.
true
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.
UTC
Example: America/New_York
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
.
100
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
.
end
Possible values: 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. Sorting by time
is useful if you request metrics for a set of asset pairs.
pair
Possible values: 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
.
Human-readable formatting of JSON responses.
false
Format of the response.
json
Possible 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.
Details
Our reported liquidations metric is an aggregation of the reported liquidations from an exchange.
Examples
A sample of the daily reported liquidation buy orders for the Binance BTCUSDT futures market is shown below:
binance-BTCUSDT-future
2022-01-01 00:00:00
84.918
binance-BTCUSDT-future
2022-01-02 00:00:00
80.595
binance-BTCUSDT-future
2022-01-03 00:00:00
74.007
binance-BTCUSDT-future
2022-01-04 00:00:00
109.399
market. The IDs of the markets.
time. The time in ISO 8601 date-time format.
liquidations_reported_future_buy_units_1d. The reported volume of liquidation buy orders in native units.
Release History
Release Version. Market Data Feed 2.6 (July 2022)
Last updated
Was this helpful?