Supported algo orders include STOP, OCO, TRAILING_STOP, POSITIONAL_TP_SL, TP_SL, BRACKET and STOP_BRACKET orders. clientAlgoOrderId behavior: needs to be unique among open algo orders. Orders with the same clientAlgoOrderId can be accepted only when the previous one is completed, otherwise the order would be rejected. Note that it’s treated separately from the clientOrderId for ordinary orders. visibleQuantity behavior: it sets the maximum quantity to be shown on orderbook. By default, it is equal to quantity. If it’s set to 0, the order would be hidden from the orderbook. Open algo order limit:
- a maximum of 100 open algo orders is allowed on a per instrument basis
- a maximum of 10 open TP_SL orders are permitted per instrument - this is inclusive of the TP_SL orders that are still attached to BRACKET or STOP_BRACKET order
- a maximum of 1 open POSITIONAL_TP_SL is allowed per instrument per side - when a second POSITIONAL_TP_SL order gets activated that’s associated with a BRACKET or a STOP_BRACKET order, this new POSITIONAL_TP_SL order will replace the previous POSITIONAL_TP_SL order
Headers
api-key
"abcdef123456"
api-signature
"signaturestring"
api-timestamp
"1718943200000"
Body
Symbol name
STOP: stop market / stop limit order
Client algo order Id as assigned by the user
An optional tag for this order, max string length: 64
BUY/SELL, not required for POSITIONAL_TP_SL or TP_SL order
BOTH for one way mode; LONG or SHORT for hedge mode; Only applicable to perpetual instruments
Order quantity, not required for POSITIONAL_TP_SL order
The order quantity shown on orderbook; for POSITIONAL_TP_SL order, visibleQuantity applies directly to the child orders
CROSS / ISOLATED
Only support LIMIT
Trigger price type, currently only support MARKET_PRICE (i.e. last price)
Trigger price, only support LIMIT
Order price, only applicable to LIMIT type
Only applicable to perpetual instruments; whether the order can only reduce in position size; valid options are true/false