Cancel orders by price (fp=), by exchange
You have a ladder of limit orders resting on one symbol, and you want to pull the one at 64,000 and keep the rest. c=order fp=64000 is the line for that. Whether Autoview cancels only that order depends on the exchange. On some, the cancel checks the price. On the rest, Autoview drops fp= from the cancel and removes every open order on the symbol that matches the rest of the line.
This page comes from the Autoview integrations code that runs on our servers today. We read the code; we did not re-run each exchange live for this guide. Test your own cancel with d=1 before you rely on it.
Exchanges that check fp= on a cancel
On these, c=order fp=X cancels only open orders whose price is X. Give a range such as fp=63000-64000 and it cancels every order priced inside it, both ends included.
| Exchange | Price the cancel compares |
|---|---|
| Alpaca, Crypto.com | The order's limit price. |
| Binance spot, Binance USD-M futures, Binance COIN-M futures, Binance.US | The order price. |
| Bitfinex, Bybit, Deribit, Gate.io spot and futures, Gemini, KuCoin spot and futures, OANDA, HTX USDT-margined swaps | The order price. |
| Capital.com | The level of the working order. |
| OKX | The order price, on plain orders and on stop and trigger orders. |
| BitMEX | The price, sent to BitMEX as an exact filter. Use one exact price here, not a range. |
Where the compared price is the limit price, a stop order with no limit price is not matched by its trigger. If you need to pull a resting stop, t=close can pick stops by type on exchanges that read it. See cancel only stops or only entries, by exchange, and check the cancel with d=1 first.
Hyperliquid, TradeStation and Tradovate: not confirmed
- Hyperliquid compares the order's limit price. We have not run it.
- TradeStation compares the price TradeStation uses for buying power on the order. We have not checked that it always equals your limit price.
- Tradovate compares a price field on the open order. We have not seen whether Tradovate's open-order list returns that field. If it does not,
fp=matches nothing and the cancel removes nothing.
Exchanges that ignore fp= on a cancel
On these, c=order fp=64000 behaves exactly like c=order. Every open order on the symbol that matches the rest of the line is cancelled, at every price.
- Bitget spot and Bitget futures
- Coinbase Advanced
- Charles Schwab
- HTX spot, HTX coin-margined futures and HTX coin-margined swaps
- Kraken and Kraken Futures
Bitget and KuCoin Futures copy trading: no cancel at all
On a Bitget copy trading account or a KuCoin Futures copy trading account, c=order cancels nothing, with or without fp=. Autoview stops the line with "Canceling Open Orders is not supported." Cancel those orders on the exchange itself. c=position still closes positions on both.
On Bitget, Kraken and Kraken Futures you can tag each order with id= and cancel by that instead. The cancel by id=, by exchange guide lists where that works.
On Coinbase Advanced, Kraken and Bitget futures, t=open or t=close can split entries from stops instead. Bitget spot, Charles Schwab, HTX and Kraken Futures ignore t= on a cancel as well. The cancel only stops or only entries guide has the full list.
Where fp= is ignored you can still limit how many orders one line cancels with cm=, and choose the oldest, newest, lowest or highest with cmo=. See cancel the oldest or newest orders.
Two things to avoid
- A percent price.
fp=1%is read as 0.01, not one percent from the market. Use a plain number. - A price that rounds differently. The match is on the price the exchange reports. If your alert sends 64000.004 and the order rests at 64000, a single price misses it. A narrow range such as
fp=63999-64001catches it.
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. If the list holds orders at other prices, your exchange is on the ignore list. The log guide shows where to look. To run several strategies on one symbol, see several strategies on one account.