Trailing stops by exchange
A trailing stop in Autoview is one parameter on your alert: ts= for a distance like ts=1%, or fts= for the fixed form. Not every exchange takes it. This page lists which ones do, which also take an activation price, and what happens when you send it somewhere it can't go.
The list comes from the Autoview integrations code that runs on our servers and in the browser extension today (version 0.40.1). If you want the syntax itself first, the stop loss, take profit and trailing stop guide covers it. For the reduce-only flag, see reduce-only orders by exchange.
Exchanges that take ts= and fts=
On these venues Autoview reads ts= or fts= and places a trailing stop with your order:
- Alpaca
- Binance, Binance Futures, Binance Delivery and Binance.US
- Bitfinex
- Bitget Mix (classic futures accounts, see the note below)
- BitMEX
- Bybit
- Capital.com
- Gate.io Futures
- HTX, HTX Futures, HTX Linear and HTX Swap
- OANDA
- OKX
- TradeStation
- Tradovate
- Charles Schwab, Deribit, Kraken and Kraken Futures (trailing distance only, no activation price)
Activation price: tsx= and ftsx=
An activation price tells the trailing stop to wait until price reaches a level before it starts to follow. In Autoview that is tsx=, or ftsx= for the fixed form.
- Read by the connector: Bybit, Gate.io Futures and OKX.
- Rejected with an error: Charles Schwab, Deribit, Kraken and Kraken Futures. These venues trail natively but have no activation price, so Autoview stops the alert instead of trailing from the wrong point.
- Not read: the other venues in the list above. They take
ts=, but their connector does not look attsx=. Leave it off on those venues.
Exchanges that reject a trailing stop
These connectors do not place trailing stops. If an alert carries ts=, fts=, tsx= or ftsx=, Autoview stops it with a Trailing Stop (ts/fts) is not supported error and links the exchange's help page:
- Bitget (spot) and Bitget Mix Copy
- Bybit Copy
- Coinbase Advanced
- Crypto.com
- Gate.io (spot)
- Gemini
- HyperLiquid
- Kucoin, Kucoin Futures and Kucoin Futures Copy
The check runs before anything goes to the exchange, and it covers every leg of an alert joined with &. So a rejected alert places nothing at all. You will not end up with an entry that has no stop behind it. Use a plain sl= stop loss on these venues, or close the trade with your own exit alert.
Two venue rules to know
- HTX: a trailing stop needs a trigger price. Send
px=orfpx=withts=, or Autoview stops the alert and asks for it. - Bitget Unified Trading Account: once Bitget moves your futures account to a UTA, Autoview rejects trailing stop and trigger price orders on Bitget Mix with an error. A classic futures account takes
ts=as normal.
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. A rejected parameter shows up there as the same error you would get live. When the log looks right, take d=1 off. The log guide shows where to look.