Hidden and iceberg orders (h=), by exchange

Autoview · Guide · Updated November 3, 2026

An iceberg order shows only part of its size on the order book. When that part fills, the exchange shows the next slice. A hidden order shows nothing at all. In an Autoview command you ask for either with h=:

b=buy p=-1% q=1 h=10%

That line asks for a limit order of 1 with a tenth of it visible. A percentage is a share of the order quantity; a plain number such as h=0.1 is a quantity. What reaches the exchange depends on the connection. Some send your visible size, one sends a hidden flag, and many do not read h= at all. 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.

Your h= becomes the visible size

These send the exchange's own iceberg field, filled with your h= measured against the order quantity:

• Binance spot. Sent as icebergQty. On an oco= order it goes on the limit leg as limitIcebergQty.
• Binance US. Sent as icebergQty. Inside an & bracket section it goes on that order's limit leg.
• BitMEX. Sent as displayQty, rounded to the contract step.
• Deribit. Sent as display_amount, rounded to the contract step. Deribit has its own limits on this (see the Deribit guide).
• Gate.io, spot and futures. Sent as iceberg on a regular order. A px= triggered order does not carry it.
• KuCoin futures. h=100% sends a fully hidden order. Any other value sends an iceberg with that visible size.
• TradeStation. Sent as ShowOnlyQuantity, rounded to the quantity step.
• Tradovate. Sent as maxShow on a single order. On an oco= line, or on an & strategy line, the order goes out without it, so the whole size shows.

Any h= means fully hidden

• Bitfinex. Any h= sets Bitfinex's hidden flag, on the entry and on a bracket exit. The number you give is not used, so h=10% and h=100% do the same thing: the order is not shown at all.

KuCoin spot: check this one first

On KuCoin spot, Autoview puts the amount you give in h= into KuCoin's hidden field. It sends no iceberg or visible-size field on spot. So you cannot ask KuCoin spot for a visible slice through Autoview, and we have not checked how KuCoin treats an amount in that field. Run the line with d=1 and place one small order before you rely on it.

Exchanges where h= is ignored

These connections never read h=. Autoview does not refuse it either, so the order goes out at full size on the book, with no warning:

• Alpaca
• Binance USD-M futures and Binance COIN-M futures
• Bitget, spot and futures
• Bybit
• Capital.com
• Charles Schwab
• Coinbase Advanced
• Crypto.com
• Gemini
• Hyperliquid
• Kraken spot and Kraken Futures
• OANDA
• OKX

This is the case to watch. If you size an order to stay out of sight, on these connections the whole quantity is visible to the market. HTX and the copy-trading connections were not checked for this page.

Keep h= on a plain limit order

An iceberg rests on the book, so it belongs on a normal limit order. Autoview does not strip h= when you add another order type. On Binance spot, for example, the iceberg size still goes out with t=ioc, t=fok or t=market. Binance's API documentation says an iceberg is "Used with LIMIT, STOP_LOSS_LIMIT, and TAKE_PROFIT_LIMIT" orders and that "Any order with an icebergQty MUST have timeInForce set to GTC". We did not send these combinations live, so leave h= off any line that also uses t=ioc, t=fok or t=market. The IOC and FOK page lists what those types send on each 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 order on a test account and look at the order on the exchange to see how much of it shows. For maker-only orders, see post-only orders by exchange. Your log shows what the exchange answered.

Open the command reference