GateData.AI

Derivatives · Liquidation events

Query executed derivatives liquidation events by venue, pair, position side, and notional value.

GET/api/v1/markets/derivatives/liquidations
Domain
Market & Liquidity
Level
Crypto asset liquidation events
MCP tool
market_data_query (task=liquidations)

Available data

Returns
Executed derivatives liquidation events by venue, pair, position side, and notional value
Market coverage
Crypto derivatives markets
Query granularity
Each row is one recorded public liquidation event; the feed may not include every liquidation inside an exchange

Authentication

Send Authorization: Bearer YOUR_API_KEY or X-API-KEY on every request.

Query Parameters

Asset positioning

Provide at least one of asset_id or query.

asset_idstringqueryExampleasset_btcconditional

Canonical asset identifier

querystringqueryExampleBTCconditional

Search text used to resolve the query object

Liquidation filters

All optional; venue_symbol filters a specific venue pair.

venuestringqueryExamplebinanceoptional

Trading venue code to query

venue_symbolstringqueryExampleBTCUSDToptional

Venue pair, e.g. BTCUSDT.

position_sideLONG | SHORTqueryExampleLONGoptional

Liquidated position side: LONG or SHORT.

min_notional_usdnumberqueryExample10000optional

Minimum liquidation notional in USD.

Time range and pagination

Times accept Unix milliseconds or RFC 3339; results use cursor pagination.

start_timestringqueryExample1789977600000optional

Start of the query time range

end_timestringqueryExample1790582400000optional

End of the query time range

limitintegerqueryExample100optional

Maximum records returned per request

cursorstringqueryoptional

next_cursor returned by the previous response.

Response

items[]object[]

Liquidation event records

liquidation_idstringExampleliq_example

GateData liquidation record identifier

event_timeintegerExample1790577523073

Event time in Unix milliseconds

venuestringExamplebinance

Venue code

venue_symbolstringExampleBTCUSDT

Venue trading pair

asset_idstringExampleasset_btc

GateData asset identifier

base_assetstringExampleBTC

Base asset symbol

position_sideLONG | SHORT | UNKNOWNExampleLONG

Liquidated position side

pricestringExample83065

Liquidation price

notional_usdstringExample12459.75

Liquidation notional in USD

next_cursorstring | nullExamplecursor_example

Cursor for the next page

has_morebooleanExampletrue

Whether another page is available

coverageobject

Requested range and data coverage

disclaimerstringExamplePublic liquidation records may not inclu…

Public liquidation data disclaimer

metadataobject

Response status and resolution information

data_statusDataStatusExampleready

Business data availability status

limitations[]string[]

Known data limitations

updated_atdatetime | stringExample2026-09-28T08:26:00Z

Most recent object or response update time

partialboolean

Whether the response contains only a subset of fields

resolution_reasonstring

Reason code for the object-resolution outcome

object_refs[]object[]

Unified object references

typeObjectRefTypeExampleasset

Object reference type

idstringExampleasset_btc

Canonical object identifier

entity_idstring

Canonical entity identifier

asset_idstringExampleasset_btc

Canonical asset identifier

listing_idstring

Canonical listing identifier

instrument_idstring

Canonical financial instrument identifier

venue_idstring

Canonical trading venue identifier

event_refstring

Related event identifier

market_idstring

Canonical market object identifier

venuestring

Related platform code

resolved_fromstring

Input used to resolve the object

resolution_confidencestring

Object resolution confidence

Errors & fallback

200
assets_resolve name multi-match; confirm from data[] candidates.
200
The object resolved but no data is available; empty_reason may be not_covered_by_source, unsupported_metric, or limited_depth.
400
Invalid parameters or an ambiguous market listing; ambiguity responses include required_params + candidates.
401
The API key is missing or invalid.
403
The current key scope or plan cannot access this data domain.
404
The requested resource does not exist; source coverage gaps are not 404 responses.
402
Credits or monthly quota exhausted.
429
Request rate exceeded; retry_after is returned in the body and Retry-After in the response headers.