Top Trader Long/Short Account Ratio History

Get the top trader long/short account ratio history for a futures trading pair on a given exchange: the shares of top trader accounts holding long and short positions, and the ratio between the two. Useful for observing the directional bias of top traders.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Available on all API plans: Hobbyist Startup Standard Professional Enterprise

The data intervals you can query differ by API plan; see API Plans and Available Intervals below on this page.

Response Data

data is an array; each element holds the data for one interval, and time is the start time of the interval. Values are returned as numbers. Only top trader accounts are counted, by number of accounts, without regard to the position size of each account.

📘

Shares Are Percentage Values; the Long/Short Ratio Is a Ratio

*_long_percent and *_short_percent are in %: 62.62 means 62.62%, so there is no need to multiply by 100, and the two add up to about 100. *_long_short_ratio is the long share ÷ the short share: 1.68 means longs are 1.68 times shorts; it is not a percentage value.

200 · application/json · See the response example in the right panel.

FieldTypeAlways ReturnedDescription
codestringYesBusiness status code; "0" means success
msgstringNoResult message
dataarray of objectYesArray sorted by time; each element is one interval
data[].timeinteger (int64)YesInterval start time, timestamp in milliseconds (UTC)
data[].top_account_long_percentnumberYesLong share among top trader accounts, in %
data[].top_account_short_percentnumberYesShort share among top trader accounts, in %
data[].top_account_long_short_rationumberYesLong/short ratio among top trader accounts: long share ÷ short share

API Plans and Available Intervals

All API plans can call this endpoint; they differ in the data intervals they can query: the lower the plan, the longer the shortest available interval. For the price of each plan, see API Plans.

API PlanAccessAvailable Data Intervals (interval Parameter)
Hobbyist✅ Yes4 hours and above: 4h, 6h, 8h, 12h, 1d, 1w
Startup✅ Yes30 minutes and above: 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 1w
Standard✅ YesAll intervals, minimum 1 minute (1m)
Professional✅ YesAll intervals, minimum 1 minute (1m)
Enterprise✅ YesAll intervals, minimum 1 minute (1m)

For how much historical data each interval can query, see Intervals.

Use This Endpoint with AI

Pick a task and click Open in ChatGPT or Open in Claude: the AI reads this page first and then gives you the result. You can also click Copy and paste the full prompt into the AI tool you use.

Fetch data with Python
Have AI write a Python function that fetches the daily top trader long/short account ratio for Binance BTCUSDT over the last 30 days.
Compare top traders with all accounts
Have AI write code that plots the top trader long/short account ratio and the all-account long/short ratio on one chart.
Understand this endpoint
Have AI explain in plain language the response fields and what the top trader long/short account ratio means.

Want AI to query real-time data without writing code? Connect CoinGlass MCP in Claude or Cursor and ask in plain language, for example: “Are top traders on Binance currently leaning long or short on BTCUSDT?”

Use Cases

ScenarioDescription
Track Top Trader DirectionThe top trader long/short account ratio shows how many top traders are bullish and how many are bearish.
Compare with Retail SentimentCompare with Global Long/Short Account Ratio History; it is worth paying attention when top traders and all accounts point in opposite directions.
Factor In Position SizeCompare with Top Trader Long/Short Position Ratio History to judge whether top traders lean long by number of accounts or by position size.
Build Quant FactorsUse changes in the top trader long/short ratio as a sentiment factor and backtest it on a single trading pair.

Related Endpoints

EndpointHow It Differs
Global Long/Short Account Ratio HistoryCounts all accounts; closer to retail sentiment
Top Trader Long/Short Position Ratio HistoryAlso covers only top traders, but calculated by position size
Coin Taker Buy/Sell RatioRatio of taker buy to taker sell trading volume (USD)
Open Interest OHLC HistoryOpen interest changes for the same trading pair
Supported Exchanges and PairsLook up valid values for symbol

FAQ

What is the difference between the top trader long/short account ratio and the top trader long/short position ratio?

The account ratio is calculated by the number of top trader accounts, with each account counting as one; the position ratio is calculated by the position size of top traders, so accounts with larger positions have more influence. The two can point in different directions.

Should I multiply a percentage field such as 64.31 by 100?

No. Fields such as top_account_long_percent are already percentage values; 64.31 is 64.31%.

Why do I get no data when I switch to another exchange or coin?

This endpoint currently supports only five exchanges: Binance, OKX, Bybit, Gate and HTX. Of these, OKX supports only XRP, BTC, LINK, FIL, BCH, ETH, ETC, ADA, LTC, DOT and TRX; Bybit supports only BTC, ETH, SOL, XRP, DOGE, TON, LTC, BCH and ADA. Also, symbol must use that exchange's trading pair format, e.g., BTCUSDT, not BTC.

Why does the number of returned data points differ from limit?

When both start_time and end_time are passed, the number of data points returned is determined mainly by the time range and interval, and can also be affected by missing data, so it does not necessarily equal limit. If you only want the most recent N data points, pass only limit and omit the start and end times.

Learn More: Top Trader Long/Short Account Ratio

What Is the Top Trader Long/Short Account Ratio?

It measures, among the top traders as defined by the exchange, the shares of accounts holding long positions and accounts holding short positions. A ratio above 1 means more top traders are bullish. Exchanges may use different criteria to define top traders, so keep this in mind when comparing across exchanges.

Why Look at Top Traders Separately?

Top traders have large amounts of capital, and their directional bias is often treated as a more useful signal than that of retail traders. It is worth paying attention when top traders and retail traders point in opposite directions, but this is only a reference and cannot be used on its own to judge whether the price will rise or fall.

How Do I See the Actual Position Bias of Top Traders?

The account count reflects only the number of traders; to see position size, use Top Trader Long/Short Position Ratio History.

Query Params
string
required
Defaults to Binance

Exchange name, e.g., Binance. Currently supports Binance, OKX, Bybit, Gate, HTX; other exchanges are not supported by this endpoint. For the pairs you can query, see the Supported Exchanges and Pairs endpoint.

string
required
Defaults to BTCUSDT

Trading pair symbol, e.g., BTCUSDT. Exchanges write trading pairs differently; for the pairs you can query, see the Supported Exchanges and Pairs endpoint. Binance, Gate and HTX support all coins; OKX supports only XRP, BTC, LINK, FIL, BCH, ETH, ETC, ADA, LTC, DOT and TRX; Bybit supports only BTC, ETH, SOL, XRP, DOGE, TON, LTC, BCH and ADA.

string
required
Defaults to 1d

Data interval, e.g., 4h. Options: 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 1w. The shortest interval you can use depends on your API plan: 4h for Hobbyist, 30m for Startup, and 1m for Standard and above.

int32
≤ 1000
Defaults to 1000

Number of data points to return; default 1000, accepts 1–1000. When both start_time and end_time are passed, the number of returned data points is determined by the time range and does not necessarily equal limit.

int64

Start time, timestamp in milliseconds (UTC), e.g., 1790812800000 (2026-10-01 00:00 UTC). The time of the returned data satisfies start_time ≤ time < end_time: the start time is included and the end time is excluded.

int64

End time, timestamp in milliseconds (UTC), e.g., 1792022400000 (2026-10-15 00:00 UTC). The time of the returned data satisfies start_time ≤ time < end_time: the start time is included and the end time is excluded. For example, with interval=1d, the two example times above return data from October 1 to October 14, 14 data points in total.

Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json