Market Level Liquidations
/timeseries/market-liquidations
Last updated
Was this helpful?
/timeseries/market-liquidations
Last updated
Was this helpful?
Exchanges which offer futures markets utilize a risk management system that will attempt to close a user’s position before the point at which the user begins to owe more than what is in the user's account. The trade or order that closes the user's position is referred to as a liquidation.
Futures contracts enable market participants to trade with leverage – that is, market participants are allowed to have a position with notional value greater than the amount of money they have in their account. This raises the possibility that market participants can lose more money than have in their account. To address this possibility, exchanges which offer futures products have a liquidation system that will attempt to close a market participant’s position before the point at which the market participant begins to owe more than what is in their account.
A simplified example illustrates the process. Suppose a trader deposits $100 into an exchange and buys $10,000 worth of Bitcoin perpetual contracts resulting in a leverage of 100x. Also, suppose the current price of Bitcoin is $10,000. If the price declines to $9,900 (the “bankruptcy price”), the trader would be bankrupt. Therefore, the exchange sets the liquidation price for this trader’s position at $9,925 (the “liquidation price”). If the price declines to this liquidation price, the exchange will forcibly initiate a sell liquidation order to attempt to close the trader’s position.
Individual market liquidations can be accessed using these endpoints:
timeseries/market-liquidations
A sample of the liquidations data from the binance-BTCUSDT-future market from our /timeseries/market-liquidations API endpoint is provided below.
market: The id of the market. Market ids use the following naming convention: exchangeName-baseAsset-quoteAsset-spot for spot markets, exchangeName-futuresSymbol-future for futures markets, and exchangeName-optionsSymbol-option for options markets. \
time: The exchange-reported time in ISO 8601 date-time format. Always with nanoseconds precision.\
coin_metrics_id: The id of a liquidation (unique per exchange). We are using exchange reported value if exchange reports a numeric liquidation id, otherwise we convert to numeric using Bijective mapping from exchange reported liquidation id’s string. For exchanges that do not report a liquidation id, we use multiple fields to create a unique liquidation id. \
amount: The amount that is liquidated in units of number of contracts.\
price: The price of the underlying base asset quoted in the underlying quote asset that the liquidation trade was executed at or liquidation order was set at.\
type: The liquidation type. trade means that the liquidation was executed. order means that the order was placed for the liquidation at the timestamp of the data entry but it wasn’t necessarily executed yet.\
database_time: The timestamp when the data was saved in the database in ISO 8601 date-time format with nanoseconds precision.\
side: The market order side of the trade or order that closes the liquidated position. buy means that an ask was removed from the book by an incoming buy order, sell means that a bid was removed from the book by an incoming sell order. We report the side of the trade or order that was used to close the position under liquidation -- not the side of the original position.
We report the side of the trade or order that was used to close the position under liquidation -- not the side of the original position. For example, if a trader had a long position and the price suddenly declined that caused the trader's position to be liquidated, the result would be a liquidation with a side of sell.
There is no set time frequency for liquidations, since they are event-based just like trades or orders. Whenever an exchange liquidates a traders position, the data is pulled in real time. In theory, if the market is trading flat and not moving much in either direction, you won't see many liquidations, whereas if there is high volatility you'll see a higher frequency stream of liquidations.
Our liquidation data harmonizes liquidation data across various exchanges. Here we discuss some differences in how various exchanges report their liquidations data.
Liquidation orders versus liquidation trades: Some exchanges report “liquidations orders” in which they will report the creation of a liquidation order when a trader’s position initially enters liquidation. When a trader’s position enters liquidation, an exchange will typically enter a limit order at the price at which the trader will be bankruptcy price. The liquidation orders will show the amount of the position that is being liquidated and the liquidation price, but will not represent the matched trades that are executed as a result of the liquidation. Other exchanges will report “liquidation trades” which represent the actual matched trades as a result of a liquidation order but will not report liquidation orders. Some exchanges will report both liquidation orders and liquidation trades.\
Aggregated liquidation trades versus individual liquidation trades: For the exchanges that report liquidation trades, the exchange can report it in aggregated or individual format. Exchanges that report liquidation trades in aggregated format means that even if the liquidation involved several matched trades, the exchange will report it as one aggregated trade representing the sum of the amount liquidated and the average price of the liquidations. Other exchanges report liquidation trades in individual trade format such that one liquidation can be reported via multiple observations representing the multiple matched trades.\
Side of original position versus side of liquidation: Most exchanges report the side of the liquidation order or trade that is used to close the user's position (i.e. whether the liquidation was a buy or sell action to close the position). Some exchanges instead report the side of the original position that is under liquidation (i.e. whether the original position that is under liquidation was a long or short position). \
With original position data versus without original position data: Some exchanges report data about the position that is liquidated such as the original quantity and the original price that the position was entered into while others do not.\
With history versus without history: Similar to trades data, certain exchanges allow us to query historical liquidation data while others do not.
We harmonize the data in the following way:
If an exchange reports both liquidation orders and liquidation trades, we store both types of observations and differentiate the two types with the type column. \
Bybit is the only exchange in our coverage universe that reports the side of the original position under liquidation. Every other exchange reports the side of the liquidation. We adopt the convention of reporting the side of the liquidation, and we map Bybit's data to this convention by inverting the side reported by Bybit.
Liquidations data from Binance are missing from 2021-04-27 to 2021-05-11 due to a breaking change that was made to the Binance API on 2021-04-27. \
Our liquidations data from Binance for an approximately four month window is underreported due to a breaking change that was made to the Binance API on 2021-04-27. Prior to this date, Binance had reported every single liquidation. Our liquidations table was using the “last filled quantity” (and price), which was appropriate when all liquidations were reported. However, the change they implemented rendered their API to only report the latest liquidation within the last 1,000ms. As a result, our scrapers logic no longer fully captures every liquidation. We implemented a change to our scrapers on 2021-08-31. Rather than using the “last filled quantity” (and price), we will be using the total quantity of the liquidated orders that happened in that 1000ms interval (and the average price of that interval). Unfortunately, all liquidations data that was captured between 2021-05-11 and 2021-08-31 will remain underreported and there is no way for us to recover the data, as Binance does not permit the collection of historical liquidations. However, all liquidations that occurred before 2021-04-27 are still accurate. \
In rare instances where OKEx reports two adjacent liquidations with identical time, amount, and price, we only stored the first observation prior to 2021-09-21. This issue was corrected on 2021-09-21. \
Our liquidations data from BitMEX are underreported prior to 2021-09-20 due to rate limits imposed by the exchange. This issue was corrected on 2021-09-20. \
Our liquidations data from Bybit were interrupted for a period of 5 days between 2021-09-24 to 2021-09-29 due to a deprecation of their API endpoint. This issue was corrected on 2021-09-29.
CM MDF v2.2 on December 2, 2020: Added liquidations for futures markets on Binance, Bitfinex, BitMEX, Deribit, FTX, Huobi, Kraken, and OKEx.\
CM MDF v2.4 on September 1, 2021: Added liquidations for futures markets on Bybit.
The previous 24 hours of liquidations data is available through our community API. Community data is available via HTTP API only and is limited to 10 API requests per 6 seconds per IP address. All of our liquidations data is available through our professional API with higher rate limits.
Futures
3817
Binance
203
2019-09-10
Bitfinex
26
2019-08-01
BitMEX
77
2020-10-08
Bybit
30
2021-04-24
Deribit
62
2018-08-14
FTX
824
2019-04-19
Huobi
1287
2020-07-10
Kraken
53
2020-12-09
OKEx
1255
2020-10-01
Returns liquidations for specified futures markets.<br/> Results are ordered by tuple (market, time).<br/> To fetch the next page of results use next_page_url JSON response field. Keep in mind that spot markets are not supported by this endpoint.
/timeseries/market-liquidations
Comma separated list of markets or market patterns like exchange-* or exchange-*-spot or *USDT-future.<br/> Use the /catalog-all/markets endpoint for the full list of supported markets.
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 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.
Inclusive or exclusive corresponding start_* parameters.
Inclusive or exclusive corresponding end_* parameters.
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.
America/New_YorkNumber 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.
Where does the first page start, at the start of the interval or at the end.
start, endHow many entries per market result should contain. It is useful when multiple markets are requested.
Human-readable formatting of JSON responses.
Format of the response.
json, csvToken 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.