Add to an open position, by exchange
You are long, the next signal fires, and you want more of the same trade. There are two ways to send that add. A plain entry such as b=long q=10% is sized from your balance, as the common strategies guide describes for scaling in. The other way is c=position with opposite=0, which sizes the add from the position you already hold and can price it off your average entry. This page covers the second way.
It comes from the Autoview integrations code that runs on our servers today. It has not been re-run live for this guide, so test your own alert with d=1 first.
How opposite=0 adds
Normally c=position closes. Its order goes out on the side that ends the position, because opposite=1 is the default. With opposite=0 the order goes out on the position's own side instead, so it grows the trade:
c=position b=long opposite=0 q=50%Three things decide what that order looks like.
- q= is measured against the position.
q=50%adds half of what you hold. Leaveq=off and it adds 100%, which doubles the position. A plain number such asq=0.01adds exactly that amount. - The price can come from your average entry. Add
ps=positionand the limit price is set from the position's average entry.ps=position p=-1%places the add 1% below it, andp=-100places it 100 below. Bitget futures, Bybit, Kraken Futures and BitMEX are the exception: therep=is dropped and the add goes out exactly at the position's price, which on BitMEX is the break-even price. To add below entry on those four, leaveps=off and send the price yourself withfp=. The price source guide has the full list. Orders are limit orders unless you sendt=market. - The order is not marked as a close. It is a normal order on the same side, so a reduce-only flag is only added if you send
ro=1. Leavero=off an add.
A long example that buys half again, 1% under the average:
c=position b=long opposite=0 ps=position p=-1% q=50%Always send b=
b= tells Autoview which position to add to. On most venues, opposite=0 without b= stops with a missing parameter error and nothing is sent.
Binance Futures, Binance Delivery, OKX, and HTX Futures, Linear and Swap build this order their own way and skip that check. On those venues a missing b= means every position open on that symbol gets an add on its own side, each sized from itself. In hedge mode with a long and a short open, both grow. On a flat account the same alert stops with an order book error, because a new entry has no side.
With nothing to add to, it opens a new trade
If no open position matches b=, opposite=0 does not stop. Autoview places a normal entry on the b= side instead. That happens on a flat account, and also when the only position open is on the other side.
The new entry is sized from your balance like any other entry, so the meaning of q= changes: q=50% is now half your balance, not half a position, and with no q= it is 100% of your balance. If you hold a short and send b=long opposite=0, the new buy offsets the short on an account that nets long and short into one position, the same as any other buy would.
This is on purpose: it lets one alert mean "add to my long, or open one if I have none". It also means an add alert that fires after the position has closed opens a fresh trade. If you only want the add, size it with a plain number such as q=0.01 so the fallback entry stays small, and check your log.
Where venues differ
Where we read the code, opposite=0 adds as described above on Alpaca, Bitfinex, Bitget futures, BitMEX, Bybit, Charles Schwab, Crypto.com, Deribit futures, Gate.io futures, Hyperliquid, Kraken margin, Kraken Futures, KuCoin Futures, OANDA, TradeStation and Tradovate, with the missing b= check in place. Binance Futures, Binance Delivery, OKX and the three HTX futures connectors add too, without that check. These are the exceptions:
| Venue | What opposite=0 does |
|---|---|
| Capital.com | With no q= or q=100% it closes the position. A full-size close always uses Capital.com's own close route, whatever opposite= says, and it skips the b= check. A smaller q=, such as q=50%, adds. |
| KuCoin Futures copy trading | Always closes. opposite= is not read on this connector. |
| Bybit copy trading, Bitget copy trading | Refused with an unsupported feature error when a position is open. With nothing open, Bybit copy trading places a new entry on the b= side, and Bitget copy trading stops because it cannot open orders. |
| Bybit, Capital.com | Adding sl=, tp= or ts= to a c=position line edits the stops on the open position instead of adding. On Bybit px= does the same. |
| Kraken, Kraken Futures | Adding ts= turns the line into a trailing stop on the other side, which protects the position rather than adding to it. |
| Deribit options | The add is sized from your balance, not from the position. |
| BitMEX | The size is measured against the position minus any resting orders on the closing side. A position fully covered by those orders counts as no position, so a new entry goes out. |
| KuCoin Futures | The add goes out at 1x leverage unless you send l=. The position's own leverage is not carried over. |
| Spot exchanges | c=position is not available on Binance, Binance.US, Bitget spot, Coinbase Advanced, Gate.io spot, Gemini, HTX spot and KuCoin spot. On spot, add with a plain buy. |
Two cases we have not traced: what Gate.io Futures and KuCoin Futures do when the exchange reports an empty position row, and how OKX picks the side of a position in net mode. Test those with d=1 before you rely on them.
Test it once before you rely on it
Add d=1 to the alert. Autoview writes what it would send to your log and places nothing. Check the side, the size against your position, and the price. Then try the same alert on a flat account so you see the fallback entry it would open. The log guide shows where to look. To close part of a position instead, see partial closes by exchange, and for closing or reversing on an opposite signal see close or reverse by exchange.