Hedge mode, by exchange
Some futures exchanges let you hold a long and a short on the same symbol at once. They call it hedge mode (OKX calls it long/short mode). In the usual one-way mode a symbol has one position, and a sell shrinks your long before it opens a short. In hedge mode the long and the short are two separate positions, and every order has to say which one it is for.
Autoview has a hedge=1 parameter, but most connections never read it. What matters more is how each connection finds out which mode your account is in. This page goes through each one. It comes from the Autoview integrations code that runs on our servers today. We read the code; we did not send these orders live for this guide.
The one rule that catches people
In hedge mode, an order with b=sell goes to the short side. It does not close your long, and adding ro=1 does not change that. What ro=1 does to the short depends on the exchange:
- Binance futures and OKX. Autoview does not send
ro=1with ab=sellorder, so the order opens a short or adds to the one you hold. - Bybit with
hedge=on the line, and Bitget unified accounts. Autoview sendsro=1as the exchange's reduce-only flag on the short side, so the order can only shrink a short. Your long stays as it is.
To close a long, send a c=position alert, which works out the side from the position you actually hold:
c=position b=longThe details per exchange follow.
Binance USD-M and COIN-M futures
- Autoview reads the mode from Binance. It asks Binance whether your account uses hedge mode and keeps the answer for five minutes. If you switch modes on Binance, give it five minutes before the next alert. If the check fails, Autoview uses the last answer it had, or one-way mode if it never had one.
- Entries. In hedge mode,
b=buygoes to the long side andb=sellto the short side. In one-way mode both go to the single position. - ro=1 is dropped in hedge mode. Autoview sends reduce-only only in one-way mode, because Binance does not take that flag in hedge mode. See reduce-only by exchange.
- c=position. The close goes to the side of the position you hold, long or short, in either mode.
What hedge=1 changes on Binance
On a plain entry line with sl= or tp=, Autoview normally turns the order around: b=buy sl=-2% sends a sell stop that protects a long. With hedge=1, the stop keeps your side, so b=buy sl=... sends a buy stop on the long side. That is a stop entry that opens or adds to the long, not a stop that protects it. The same holds in one-way mode; hedge=1 changes the side of the stop whatever mode the account is in.
hedge=1 also stops close=1 from becoming Binance's close-position stop on an entry line. Without it, close=1 on a stop-market or take-profit-market line closes the whole position when it triggers.
Bybit
- Autoview does not read the mode from Bybit. It goes by your alert. If
hedge=is on the line, the order goes to the long side forb=buyand the short side forb=sell. Without it, the order goes to the one-way position on futures and perpetuals. On a hedge-mode account, puthedge=1on every line. - Any value counts. Bybit's connection only checks that
hedge=is there, sohedge=0does the same ashedge=1. Leave it off for one-way mode. - c=position. Autoview looks up the side of the position you hold, but it only sends that side when
hedge=is on the close line too. A hedge-mode close withouthedge=goes out as a one-way order. - Moving stops on a position. A
c=positionline withsl=,tp=,ts=orpx=changes those orders on the open position and always names the position's own side. See editing open orders by exchange.
OKX
- Autoview reads the mode from OKX. It asks OKX for your account's position mode and keeps the answer for 60 seconds. If OKX does not answer, Autoview uses net (one-way) mode, OKX's default.
- Entries. In long/short mode,
b=buygoes to the long side andb=sellto the short side. In net mode both go to the one position. - c=position. The close goes to the side of the position you hold.
hedge=is not read on OKX.
Bitget futures
- c=position. Autoview reads the mode from the position itself and closes that side. On a hedge-mode close it sets the order up the way Bitget expects for closing that side.
- Entries on a unified account. Autoview asks Bitget for the account's hold mode before the order. In hedge mode the order names the long side for
b=buyand the short side forb=sell. In one-way mode a close is sent as reduce-only. - Entries on a classic account. Every order is marked as an open, or as a close on a
c=positionline. Autoview does not check the mode first on these entries. - Leverage. On a unified account in hedge mode,
l=sets the leverage only for the side you are trading. See leverage by exchange. hedge=is not read on Bitget.
KuCoin Futures copy trading
- hedge=1 is read here. With it,
b=buygoes to the long side andb=sellto the short side. - ro=1 flips the side. With
hedge=1 ro=1,b=sellreduces your long andb=buyreduces your short. - Closing everything. A close-all line with
hedge=1must also sayb=buyorb=sell, to pick the long or the short. Without it the line is refused.
Plain KuCoin Futures (not copy trading) never sends a position side and does not read hedge=.
Every other exchange
No other Autoview connection reads hedge= or sends a position side with the order. Each order goes to the symbol's single position. Bybit copy trading and Bitget copy trading close by the side of the position they track; they are not covered in detail here.
Test it once before you rely on it
Add d=1 to see how Autoview reads your line without sending it. Then place one small order on a test account in the mode you plan to use, and check which side the exchange shows the position on. For how a close and a reversal work, see close or reverse on an opposite signal.