Global Long/Short Account Ratio History

Get the long/short ratio history across all accounts for a futures trading pair on an exchange: the share of accounts holding longs, the share holding shorts, and the ratio between the two. Useful for seeing whether overall retail sentiment leans long or short.

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 is the data for one interval, and time is the start time of the interval. Values are returned as numbers. The statistics here cover all accounts for the trading pair and are calculated by number of accounts, regardless of each account's position size.

📘

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[].global_account_long_percentnumberYesLong share among all accounts, in %
data[].global_account_short_percentnumberYesShort share among all accounts, in %
data[].global_account_long_short_rationumberYesLong/short ratio among all 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.

Get data with Python
Have AI write a Python function that gets the hourly account long/short ratio for Binance BTCUSDT over the last 7 days.
Build an extreme long/short ratio alert
Have AI write a script that alerts when the account long/short ratio is too high or too low.
Understand this endpoint
Have AI explain the response fields and what the account long/short ratio means in plain language.

Want AI to query real-time data without writing code? Connect CoinGlass MCP in Claude or Cursor and ask in plain language, for example: “What is the current account long/short ratio of BTCUSDT on Binance? Has it been rising or falling over the past week?”

Use Cases

ScenarioDescription
Gauge Retail SentimentThe long/short ratio across all accounts reflects the directional preference of most traders; the higher the ratio, the more accounts hold longs.
Look for Contrarian SignalsWhen the long/short ratio stays at an extreme high or low for a long time, the market is often too crowded on one side, which can serve as a contrarian reference.
Compare with Top TradersCompare with Top Trader Long/Short Account Ratio History to see whether retail traders and top traders agree.
Build Quant FactorsUse changes in the long/short ratio and how far it deviates from its mean as sentiment factors, and backtest them together with price.

Related Endpoints

EndpointHow It Differs
Top Trader Long/Short Account Ratio HistoryCounts top trader accounts only, calculated by number of accounts
Top Trader Long/Short Position Ratio HistoryCounts top traders only, calculated by position size
Coin Taker Buy/Sell RatioRatio of taker buy to taker sell trading volume
Open Interest OHLC HistoryChanges in open interest for the same trading pair
Supported Exchanges and PairsLook up the accepted values of symbol

FAQ

What does a long/short ratio of 1.68 mean?

It means the number of accounts holding longs is 1.68 times the number of accounts holding shorts. It is calculated only by number of accounts and does not mean that longs have 1.68 times as much capital as shorts.

Do percentage fields such as 62.62 need to be multiplied by 100?

No. Fields such as global_account_long_percent are already percentage values; 62.62 is 62.62%.

Why can't I get data when I switch to another exchange?

This endpoint currently supports only five exchanges: Binance, OKX, Bybit, Gate and HTX. Also, symbol must be the trading pair as written by that exchange, e.g., BTCUSDT, not BTC.

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

When both start_time and end_time are passed, the number of data points returned is mainly determined by the time range and interval, and is also 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: Futures Long/Short Account Ratio

What Is the Account Long/Short Ratio?

The account long/short ratio is the number of accounts holding longs divided by the number of accounts holding shorts. It reflects how many people are bullish and how many are bearish, not how much capital each side has committed.

Does a High Long/Short Ratio Mean Price Will Rise?

Not necessarily. A high long/short ratio only means that many accounts are bullish. When longs are too concentrated, a price drop can easily trigger a cluster of long liquidations. The long/short ratio works better as a sentiment reference and should be judged together with open interest and price.

How Is the Account Long/Short Ratio Different from the Top Trader Long/Short Ratio?

The account long/short ratio counts all accounts and is closer to retail sentiment; the top trader long/short ratio counts top traders only. See Top Trader Long/Short Account Ratio History and 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. This endpoint sets no additional coin restrictions for any of Binance, OKX, Bybit, Gate and HTX; if the trading pair does not exist on that exchange, an error is returned.

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