What does px= do in an Autoview command?

It sets a trigger price. On most connections that read it, the order does not go on the book until the market reaches that price. p= stays the limit price of the order that is then placed, and t=market makes it a market order on most venues.

Which exchanges ignore px=?

Binance USD-M and COIN-M futures, Bitget spot, Deribit, KuCoin spot and KuCoin futures never read px=, so the order goes out at once as a normal order. On Alpaca and Binance spot, px= is read only inside a bracket or oco= order.

Can I use t=post or t=ioc on a px= line?

Only on some exchanges. Coinbase, Gate.io (except t=ioc), Hyperliquid, OKX and Bitget futures drop the flag when px= is present. Gemini keeps it, but Gemini's API says stop-limit orders take no options, so leave it off there.

Does h= work on a trigger order?

On BitMEX, Bitfinex, TradeStation and Tradovate the hidden or iceberg setting stays on the px= order. Gate.io drops it on a px= line. Most other connections never read h= at all.

Trigger orders (px=), by exchange

Autoview · Guide · Updated November 3, 2026

A trigger order waits off the book until the market reaches a price you set, then places your order. In an Autoview command that price is px=:

b=buy q=1 fpx=70000 fp=70100

That line asks for a buy that waits until the price reaches 70000 and then places a limit at 70100. px= takes an offset or a percentage from the current price, the same way p= does, and fpx= takes an absolute price. With t=market the triggered order is a market order on most venues. What the exchange receives, and which of your other settings come along, depends on the connection. This page lists each one. It comes from the Autoview integrations code that runs on our servers today. We read the code; we did not send these orders live for this guide.

What a px= line sends

Bitfinex. A STOP (with t=market) or a STOP LIMIT whose limit is your order price. px= together with tp=, sl= or ts= is refused.
BitMEX. A Stop or StopLimit with stopPx at your trigger. A tp=, sl= or ts= on the same line replaces it.
Bybit. A conditional order: your limit or market order with a trigger price, a direction worked out from where the trigger sits against the market, and pxs= as the trigger source. On spot it is marked as a stop order.
Coinbase Advanced. A stop limit, good-til-cancelled (good-til-date with dt=). This is checked first, so t=market with px= still sends a stop limit.
Crypto.com. A STOP_LIMIT, or STOP_LOSS with t=market, sent to Crypto.com's advanced order endpoint. pxs= picks the trigger price source, mark price by default.
Gate.io, spot and futures. A price-triggered order that places a limit at your p= price when the trigger is hit. It expires after et= seconds, or 30 days.
Gemini. An exchange stop limit with your trigger as the stop price.
Hyperliquid. A trigger order, market or limit by t=market. Autoview marks it as a take profit or stop loss from which side of the market the trigger sits on.
Kraken spot. A stop-loss (with t=market) or a stop-loss-limit whose second price is your limit. Any sl= or tp= value on the same line is not sent.
Kraken Futures. Your order type stays as it is (limit, market, IOC, FOK or post) and Autoview adds a stop price. Any sl= or tp= on the same line is not sent.
OANDA. A STOP order at your trigger.
OKX. One trigger order on OKX's algo endpoint, with your trigger and your limit price. No order is placed until it fires. Without oco=, any sl= or tp= on the line is not sent.
TradeStation. A StopMarket (with t=market) or StopLimit.
Tradovate. A Stop (with t=market) or StopLimit, from a px= on the main line. A px= only inside an & section does not change the entry.
Bitget futures. A plan order with your trigger, filled at your limit price, or at market with t=market. On a Bitget Unified Trading Account, px= is refused.
Capital.com. A STOP working order at your trigger level. With t=market the stop has no level set, so check this one with d=1 first.

Which price the trigger watches, last, mark or index, is set with pxs= on Bybit, BitMEX, Bitget futures, Crypto.com and Gate.io Futures. Trigger price source (pxs=) by exchange lists what each value becomes and where it is ignored.

Exchanges where px= adds a stop price but not a stop type

On these two, Autoview adds your trigger as a stop price but leaves the order a normal limit or market order:

Binance US. The order stays LIMIT, MARKET or LIMIT_MAKER, with a stopPrice added. (sl= and tp= do set a stop type on Binance US.)
Charles Schwab. The order stays LIMIT or MARKET, with a stop price added.

We did not send these live and have not checked how each broker treats a stop price on a plain order. Do not rely on px= as a trigger here until you have tested one small order.

Exchanges where px= is ignored

These connections never read px=. The order goes out at once as a normal order:

Binance USD-M futures and Binance COIN-M futures
Bitget spot
Deribit
KuCoin spot and KuCoin futures

On Alpaca, px= is read only inside an sl= plus tp= (or oco= / oto=) bracket, as the stop leg's limit. On Binance spot, it is read only with oco=, as the stop leg's trigger. HTX and the copy-trading connections were not checked for this page.

What stays on a px= line

Some settings travel with the trigger order and some are dropped without a warning.

t=ioc and t=fok

Kept: Bybit, Crypto.com, Kraken spot, Kraken Futures, TradeStation, Tradovate, OANDA, Charles Schwab and Binance US.
Only t=ioc kept: Gate.io, spot and futures. t=fok becomes a good-til-cancelled limit.
Dropped: Bitfinex (the stop limit type replaces it), Hyperliquid, OKX and Bitget futures.
Kept, but leave it off: Gemini. Autoview still attaches the option, and Gemini's API documentation says "No options can be applied to stop-limit orders at this time."
Never read on any line: BitMEX, Capital.com and Coinbase Advanced. See IOC and FOK orders by exchange.

On OANDA, IOC and FOK stay on the STOP order. OANDA's order reference describes a stop order's time in force without listing which values it allows, and we did not test this, so check it with one small order.

tif=

On Bybit, Crypto.com, Kraken spot and OANDA, tif=ioc or tif=fok stays on a px= line, the same as without one.

t=post (post-only)

Kept: Bitfinex, BitMEX, Bybit, Crypto.com, Kraken spot, Kraken Futures and TradeStation.
Dropped: Coinbase Advanced, Gate.io, Hyperliquid, OKX and Bitget futures. The triggered order can fill as a taker.
Kept, but leave it off: Gemini, for the same reason as above.
No real post-only flag on any line: see post-only orders by exchange.

h= (hidden and iceberg)

Kept: BitMEX (display size), Bitfinex (hidden flag), TradeStation and Tradovate.
Dropped: Gate.io. Its px= order carries no iceberg size.
Never read on any line: most other connections. See hidden and iceberg orders by exchange.

Test it once before you rely on it

Add d=1 to see how Autoview reads your line without sending it, then place one small trigger order on a test account and look at the open orders on the exchange: the order type, the trigger price, and whether your post-only or time-in-force setting is shown. Your log shows what the exchange answered.

Open the command reference