TradePortfolio
DocsLiquidation History
Docs

Liquidation History

Dev

GET /liquidations/history

Historical liquidation long/short USD totals bucketed by date and exchange. Returns a chronological series of daily (or hourly, for the 1d range) liquidation volumes broken down per venue. Use it to chart long-term liquidation trends, identify historically heavy deleveraging days, or correlate liquidation spikes with price movements.

Authentication

Requires Dev tier or higher. Dev: maximum 30 days. Pro and Team: full stored history. Requests exceeding your tier's limit are clamped and a notice is included in the response.

Parameters

Query parameters

NameTypeRequiredDescription
rangestring–1d, 7d, 30d, or 90d. Defaults to 30d. 1d uses hourly buckets; others use daily buckets. Cannot be combined with start/end.
startstring–Custom window start. Must be provided with end. Dev is clamped to the rolling 30-day lookback.
endstring–Custom window end. Must be after start.

Tier behavior

  • Dev: Maximum 30 days. Requests for 90d or older custom windows are clamped to the rolling 30-day lookback; a notice is included in the response.
  • Pro/Team: Full stored historical lookback.

Example request

bash
curl -H "X-Api-Key: lk_live_your_key_here" \
  "https://api.loris.tools/liquidations/history?range=7d"

Example response

json
{
  "unit": "usd",
  "resolution": "1d",
  "data": [
    {
      "timestamp": "2026-06-01T00:00:00Z",
      "date": "2026-06-01T00:00:00Z",
      "exchanges": {
        "binance": { "long_usd": 145000000, "short_usd": 62000000 },
        "bybit": { "long_usd": 87000000, "short_usd": 31000000 }
      }
    },
    {
      "timestamp": "2026-06-02T00:00:00Z",
      "date": "2026-06-02T00:00:00Z",
      "exchanges": {
        "binance": { "long_usd": 98000000, "short_usd": 44000000 },
        "bybit": { "long_usd": 72000000, "short_usd": 28000000 }
      }
    }
  ],
  "notices": []
}

Errors

  • 400 — Invalid range value, invalid start/end, or range combined with start/end.

For authentication errors (401) and rate limit responses (429), see Errors.

Related