Cancel only stops or only entries (t=open, t=close), by exchange
Your entry limit has not filled, your stop is resting under it, and your strategy wants the entry gone. c=order on its own cancels both. On many exchanges you can narrow it with t=:
c=order t=openThat line cancels the entry orders and keeps the stop. c=order t=close does the reverse. The catch is that not every exchange reads t= on a cancel, and the ones that do disagree on what counts as a close order. This page comes from the Autoview integrations code that runs on our servers today. We read the code; we did not run each exchange live for this guide. Test your own line with d=1 before you rely on it.
Exchanges that read t=open and t=close
They split three ways on what a close order is.
Close means anything that is not a plain limit
- Binance spot, Binance.US, Crypto.com, OANDA, TradeStation.
t=opencancels plain limit orders only.t=closecancels everything else: stops, take-profits, trailing stops. - On Binance spot, a post-only limit (LIMIT_MAKER) is not a plain limit, so it counts as close.
Close means a stop
- Alpaca and Deribit count an order as close when its type is a stop (stop, stop limit, trailing stop). A take-profit limit on Deribit is not a stop, so
t=opencancels it along with your entries. - Coinbase Advanced counts an order as close when it carries a stop price.
- Kraken counts take-profit, stop-loss and trailing-stop orders as close.
- KuCoin spot counts stop orders as close. It also keeps only limit-type orders unless you send
t=market, sot=closeskips a stop that triggers a market order.
Close means an order that reduces your position
- Binance USD-M and COIN-M futures. In hedge mode, an order on the opposite side of its position side is a close. In one-way mode, a reduce-only or close-position order is a close. A plain reduce-only limit counts as close here, and a stop that would open a position counts as open.
- Bitget futures uses the order's own open or close flag.
Exchanges with their own value
- KuCoin Futures reads
t=openandt=stop, nott=close. Sendc=order t=closethere and the filter does nothing: every matching order is cancelled. Uset=stopto cancel only stops. - Capital.com reads
t=stopto cancel stops only. It does not readt=openort=close.
Not confirmed: Bybit and BitMEX
Bybit and BitMEX both have a t=open / t=close filter, but it runs only when Autoview marks t= as one you typed. When we ran Autoview's command parser on its own, it did not mark a typed t= that way, because t= also has a default value. If the live path behaves the same, the filter is skipped and both exchanges cancel every matching order. We have not confirmed which way it goes live. Run your line with d=1 first and read what it would cancel.
Exchanges that ignore t= on a cancel
On these, c=order t=open and c=order t=close cancel every open order that matches the rest of the line, entries and stops alike:
- Bitget spot, Bybit copy trading, Charles Schwab, Gate.io spot and futures, Gemini, HTX spot, futures and swaps, Hyperliquid, Kraken Futures, OKX and Tradovate.
- Bitfinex reads only
t=marketon a cancel, not open or close.
To keep a stop on these, narrow the cancel another way: by tag with id=, by price with fp=, or by count with cm= and cmo=. Check first that your exchange reads the one you pick.
Two things to watch
- Send one value.
t=open,closebecomes a list, which matches neither value, so the filter does nothing and everything matching is cancelled. - Some exchanges also narrow by stop type. Adding
sl=,tp=orts=to a cancel line keeps only that kind of order on Kraken, OANDA, BitMEX and Bitfinex, andts=alone works on a few more. The rules differ and most exchanges ignore these on a cancel. See cancel only stop-loss, take-profit or trailing orders.
Test it once before you rely on it
Add d=1 to your cancel line. Autoview lists each order it would cancel in your log and cancels nothing. The log guide shows where to look. For how stops and take-profits are placed in the first place, see stop loss, take profit and trailing stop.