---
title: "Liquidations By Exchange"
method: GET
path: "/api/v1/market-intelligence/liquidations/by-exchange"
tags: ["Market Intelligence"]
---

# Liquidations By Exchange

`GET /api/v1/market-intelligence/liquidations/by-exchange`

## Request

- Base URL: `https://cryptodataapi.com`
- URL: `https://cryptodataapi.com/api/v1/market-intelligence/liquidations/by-exchange`
- Auth: API key in header `X-API-Key`

Liquidations broken down by exchange (BTC, trailing 4h).

Rows are ``{exchange, symbol, total, total_usd, long_usd, short_usd}``,
largest first. ``total`` is the legacy CoinGlass field name; ``total_usd``
mirrors it under the naming the rest of the liquidation surface uses.

Coverage is the venue subset we stream (OKX + Bybit + Hyperliquid), so totals
run UNDER a true all-exchange number — same caveat as ``/liquidations``.
Binance geo-blocks its liquidation stream from our IPs.

The 503 below is a real cold-start signal, not a dead endpoint: this served
it on EVERY call from the 2026-07-24 CoinGlass retirement until 2026-08-22,
because the free-source cutover left the slot unsourced on the assumption
that consumers tolerate ``None`` — which is true of the other retired slots
and false here. Now it only fires while the 4h window has no venue-tagged
events, i.e. the first minutes after a deploy.

## Response `200`

Successful Response

- MarketIntelligenceDataResponse: Generic market intelligence data wrapper.
  - `data` unknown, required

---

[API](https://skmtc.dev/cryptodataapi/apis/crypto-data-api.md) · [All operations](https://skmtc.dev/cryptodataapi/apis/crypto-data-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cryptodataapi/apis/crypto-data-api/revisions/8628b754ca81?raw)