Reduce-only orders by exchange
A reduce-only order can shrink a position or close it, but it can never open one or make it bigger. In Autoview you ask for it with ro=1 on the alert. Say your exit alert fires twice, or after a stop has already closed the trade: with ro=1 the exchange refuses the extra order instead of opening a fresh position the other way.
Not every exchange gets the flag. This page lists where Autoview sends it, the venue rules that change it, and what happens on the rest. It comes from the Autoview integrations code that runs on our servers today, read venue by venue.
Exchanges where ro=1 is sent
On these venues Autoview adds the exchange's own reduce-only setting to the order when the alert carries ro=1:
- Binance Futures and Binance Delivery (One-way Mode only, see below)
- Bitfinex
- Bitget Mix
- Bybit (derivatives; see the spot note below)
- Crypto.com (derivatives only)
- Deribit
- Gate.io Futures
- HTX Linear
- HyperLiquid
- Kraken and Kraken Futures
- Kucoin Futures and Kucoin Futures Copy
- OANDA
- OKX
Venue rules to know
- Binance Futures and Binance Delivery: Autoview checks your position mode first. In One-way Mode it sends
reduceOnly. In Hedge Mode it leaves the flag off, because there the position side already decides which position the order closes. - Bybit spot: Autoview sends the flag, but Bybit ignores it on spot orders. The order goes through as a plain order. The Bybit spot command reference has the detail.
- Crypto.com: the flag only applies to derivatives. On a spot pair it is not used.
- OANDA:
ro=1sets the order's position fill to reduce only. Without it, OANDA uses its default fill. - Kucoin Futures Copy in hedge mode:
ro=1targets the opposite position side, so a sell withro=1reduces your long.
Exchanges that do not read ro=
These connectors do not look at ro=:
- Alpaca
- Binance (spot) and Binance.US
- Bitget (spot), Bitget Mix Copy and Bybit Copy
- Capital.com
- Coinbase Advanced
- Gate.io (spot)
- Gemini
- HTX (spot), HTX Futures and HTX Swap
- Kucoin (spot)
- TradeStation
- Tradovate
- Charles Schwab (single orders; the reduce-only line for the main order is switched off in the code)
This is the part to watch. Unlike an unsupported trailing stop, ro=1 on these venues does not stop the alert and does not write an error. Autoview places the order as a normal order. If your exit fires twice, the second one can open a position. On these venues, build the exit as a close of the position rather than a plain opposite-side order, so a repeat has nothing left to act on. On Capital.com that is c=position, covered in its command reference; the command reference lists the close options for the other venues.
Test it once before you rely on it
Add d=1 to the alert first. Autoview writes what it would send to your log and places nothing, so you can see whether the reduce-only setting is on the order. When the log looks right, take d=1 off. The log guide shows where to look, and trailing stops by exchange covers the same question for ts=, and OCO orders by exchange covers oco=. To close only part of a position, see partial closes by exchange.