How to Set a Trailing Stop for BTC Futures on OKX

Trailing Stop Mechanics on OKX Futures

1. A trailing stop on OKX BTC futures is a dynamic order type that adjusts its trigger price automatically as the market moves in the trader’s favor, maintaining a fixed distance—measured in price or percentage—from the current best bid or ask.

2. The system recalculates the trailing reference price every time the market ticks, but only updates the stop order’s activation threshold when the new level improves upon the previous one—never retracts it.

3. Trailing stops are available exclusively for USDⓈ-M and COIN-M perpetual and quarterly futures contracts, not for spot or options markets.

4. Users must specify either a trailing deviation value (in USDT or BTC) or a trailing deviation percentage, depending on the contract type and interface selected.

5. Once triggered, the order executes as a market order by default unless configured otherwise in advanced settings—such as converting to a limit order with a specified price offset.

Step-by-Step Configuration via Web Interface

1. Navigate to the BTC-USDT-SWAP or BTC-USD-SWAP trading page, select “Futures” tab, then click “Order” to open the order panel.

2. Choose “Trailing Stop” from the order type dropdown menu—this option appears only after selecting “Sell” or “Buy” direction and confirming leverage mode.

3. Input the initial quantity in BTC or USDT, then enter the trailing deviation: for USDⓈ-M contracts, this is denominated in USDT; for COIN-M, it is expressed in BTC.

4. Set the activation price manually or allow OKX to auto-populate it based on the latest mark price—this determines the earliest point at which the trailing logic begins tracking.

5. Click “Place Order”. The order appears under “Open Orders” with status “Pending”, displaying live updates of the current trailing reference price and deviation gap.

API Implementation Using python-okx

1. Initialize the TradeAPI instance with valid credentials and set tdMode to cross or isolated, matching the margin mode used in the target position.

2. Construct the order parameters dictionary with instId = “BTC-USDT-SWAP”, side = “buy” or “sell”, ordType = “tsl”, and include slTriggerPx, slOrdPx, and slTriggerPxType = “last” or “mark”.

3. Specify slTrailPx to define the trailing deviation in quote currency units—e.g., 200 for USDⓈ-M means the stop trails 200 USDT behind the highest/lowest price reached since activation.

4. Submit using tradeAPI.place_order(). Response includes ordId, state, and slTriggerPx—which may differ from the submitted value due to rounding or price alignment rules.

5. Monitor execution status via tradeAPI.get_orders_pending() or subscribe to WebSocket channel orders-algo for real-time updates on trailing stop adjustments and triggers.

Risk Parameters and Platform Constraints

1. Minimum trailing deviation is 0.1% for BTC perpetuals on USDⓈ-M and 0.0001 BTC for COIN-M contracts—values below these thresholds will be rejected with error code 51000.

2. Trailing stops cannot be placed within 0.5% of the current mark price for long positions or 0.5% above for short positions—OKX enforces this to prevent immediate triggering.

3. Each API key is limited to 20 active trailing stop orders across all instruments; exceeding this limit returns error 58007.

4. If the underlying contract undergoes a funding rate settlement or index price rebalance during trailing operation, the reference price resets only if the event causes a discontinuity greater than 2% in the mark price—otherwise, tracking continues uninterrupted.

5. Trailing stop orders do not support partial fills; they execute fully or remain pending until triggered or canceled.

Frequently Asked Questions

Q: Can I modify the trailing deviation after placing the order? No. OKX does not allow modification of slTrailPx or slTriggerPx post-submission. You must cancel and replace the order with updated parameters.

Q: Does the trailing stop remain active during maintenance or system upgrades? Yes. Trailing logic operates server-side and persists through scheduled maintenance windows. However, no new price ticks are processed during downtime, so the reference price freezes until service resumes.

Q: What happens if my position is liquidated before the trailing stop triggers? Liquidation takes precedence. The position closes immediately at the bankruptcy price, and any pending trailing stop order is automatically canceled without execution.

Q: Is the trailing stop price visible to other market participants? No. Trailing stop configurations—including deviation values and activation thresholds—are stored privately on OKX servers and never broadcast to the order book or public APIs.