CoinGlass API data can be queried in two ways: by coin, for aggregated market-wide data, or by a specific trading pair on a specific exchange, for detailed data. This page explains the difference between the two, how to write the parameters, and how to get the lists of supported exchanges and trading pairs.
| Item | Details |
|---|---|
| Coin aggregation | symbol=BTC returns the coin's combined data across exchanges; some endpoints use exchange_list to specify which exchanges are included in the aggregation |
| Trading pair | exchange=Binance&symbol=BTCUSDT returns data for a single trading pair on a single exchange |
| Exchanges covered | 30 futures, 11 spot, 4 options |
| Name format | Use the names as returned by the Supported Exchanges and Pairs endpoint |
Two Ways to Query
| Query Type | Purpose | Description |
|---|---|---|
| Coin aggregation | The total for one coin across all exchanges | Suited to viewing the whole market: total Bitcoin open interest, total liquidations across the market. Parameter example: symbol=BTCEndpoint examples: Aggregated Open Interest OHLC History, Coin Liquidation History |
| Trading pair | A specific contract on a specific exchange | Suited to viewing a single market: the funding rate of the BTCUSDT perpetual contract on Binance. Parameter example: exchange=Binance, symbol=BTCUSDTEndpoint examples: Open Interest OHLC History, Funding Rate OHLC History |
How do you tell which query type an endpoint uses? Look at its parameters:
- Coin aggregation: set
symbolto a coin, e.g.BTC. Some endpoints also requireexchange_listto specify the exchanges included in the total, e.g.Binance,OKX,Bybit, as in Coin Liquidation History. - Trading pair: pass both
exchangeand asymbolin trading pair form, e.g.exchange=Binance,symbol=BTCUSDT.
Endpoint names often contain “Aggregated”, “Coin” or “Pair”, which can also serve as a hint. The required parameters of each endpoint are as stated on its endpoint page.
Pass names exactly as returnedEach exchange has its own trading pair naming rules. Pass both exchange names and trading pair names exactly as returned by the Supported Exchanges and Pairs endpoint.
Supported Exchanges
The table below lists the exchanges currently covered. It changes as the market changes, so in your code rely on what the endpoints return in real time.
| Market | Count | Exchanges |
|---|---|---|
| Futures | 30 | Binance, OKX, Bybit, CME, Bitget, Deribit, BitMEX, Bitfinex, Gate, Kraken, KuCoin, dYdX, CoinEx, BingX, Coinbase, Crypto.com, Hyperliquid, Bitunix, MEXC, HTX, WhiteBIT, Aster, Lighter, EdgeX, Drift, Paradex, Extended, ApeX Omni, LBank, tradeXYZ |
| Spot | 11 | Binance, OKX, Bybit, Coinbase, Bitfinex, Kraken, Gate, Bitget, Bitstamp, Crypto.com, Upbit |
| Options | 4 | Deribit, Binance, OKX, Bybit |
Get the Latest Lists from the Endpoints
| Endpoint | Returns | Recommended Refresh Frequency |
|---|---|---|
| Supported Coins | All futures coins available for query | Daily |
| Supported Exchanges | All futures exchanges | Daily |
| Supported Exchanges and Pairs | Trading pair names on each exchange | Hourly |
| Delisted Exchanges and Pairs | Trading pairs that have been delisted and are no longer updated | Daily |
Cache these lists on your server and refresh them at the frequencies in the table above; there is no need to fetch them again before every request.
curl --request GET \
--url 'https://open-api-v4.coinglass.com/api/futures/supported-exchange-pairs' \
--header 'CG-API-KEY: YOUR_API_KEY'import os
import requests
resp = requests.get(
"https://open-api-v4.coinglass.com/api/futures/supported-exchange-pairs",
headers={"CG-API-KEY": os.environ["COINGLASS_API_KEY"]},
timeout=10,
)
print(resp.json())FAQ
Which exchanges are included in coin-aggregated data?
Aggregated endpoints with an exchange_list parameter aggregate only the exchanges you specify; those without this parameter aggregate the markets that the endpoint has integrated and that have data. In both cases, exchanges without a matching trading pair or without data are not counted, so the result does not necessarily include every market on every exchange. Misspelled or unsupported exchange names in exchange_list are ignored and do not necessarily cause an error, so first check the names with Supported Exchanges and Pairs.
For open interest data, use Aggregated Stablecoin-Margined Open Interest (OHLC) and Aggregated Coin-Margined Open Interest (OHLC) to view stablecoin-margined and coin-margined open interest respectively. Supported exchanges and trading pairs: for futures, get the list of supported exchanges and trading pairs from the Supported Exchanges and Pairs endpoint; for spot, get it from the Spot Supported Exchanges and Pairs endpoint.
What should I do if a trading pair query returns empty data?
First use Supported Exchanges and Pairs to confirm how the exchange and trading pair names are written, then check whether the pair is in the Delisted Exchanges and Pairs list. Some trading pairs that have not been integrated yet also return an empty array, e.g. Binance spot BTCUSD.
Get Crypto Futures Data by Exchange
Binance, OKX, Bybit Futures Data
Pass exchange=Binance and the corresponding trading pair to a trading pair endpoint to query that exchange's open interest, funding rate, long/short ratio and liquidation data; when you don't need to distinguish between exchanges, use the coin-aggregated endpoints.
Hyperliquid and Decentralized Perpetual Futures Data
Besides centralized exchanges, coverage also includes on-chain perpetual futures platforms such as Hyperliquid, dYdX, Aster, Lighter, Drift and Paradex. Hyperliquid also has dedicated endpoints such as Hyperliquid Whale Alerts and wallet PnL distribution.
CME Bitcoin Futures and Crypto Options Data
Futures data includes CME Bitcoin futures; options data covers Deribit, Binance, OKX and Bybit. You can use them to compare open interest changes between traditional financial markets and crypto-native markets, for example with Options Max Pain.
Related Docs
- Intervals: Values of the candle interval parameter
- Aggregated Open Interest OHLC History: Market-wide open interest API
- Funding Rate Arbitrage: Cross-exchange funding rate comparison
- Error Codes and Rate Limits: Return codes and rate limiting
