How to Use OKX Stop Loss and Take Profit Orders?

Understanding Trigger-Based Order Mechanics

1. Trigger orders operate independently from open positions until explicitly linked via the cxlOnClosePos flag.

2. The system evaluates triggerPx against real-time market data using configurable price types: last, index, or mark.

3. When the trigger condition activates, the platform submits a new order at orderPx, which may be set to -1 for market execution.

4. No margin is reserved in advance for these orders, allowing capital efficiency during idle periods.

5. Each attached algorithmic order must specify either tpTriggerPx and tpOrdPx or slTriggerPx and slOrdPx, with strict mutual dependency enforced by the API.

Structuring Multi-Condition Algo Orders

1. The attachAlgoOrds array accepts up to two entries—one for take profit and one for stop loss—enabling simultaneous bilateral setup.

2. Once one leg triggers, the counterpart automatically cancels, preserving position integrity without manual intervention.

3. Parameter validation occurs server-side; invalid combinations return HTTP 400 with descriptive error codes like 51000 or 51001.

4. Order identifiers such as attachAlgoClOrdId remain optional but improve traceability across logs and debugging sessions.

5. All values inside attachAlgoOrds must be strings, even numeric thresholds like slTriggerPx and tpOrdPx.

Position Linkage Behavior

1. Setting cxlOnClosePos to true binds the algo order lifecycle directly to the associated position’s existence.

2. Full position closure triggers immediate cancellation of all related stop loss and take profit orders regardless of their activation state.

3. When cxlOnClosePos is false, orders persist independently and may execute even after position liquidation.

4. This flag applies uniformly across all entries within attachAlgoOrds; mixed linkage modes are unsupported.

5. Position-side alignment (posSide) must match between the parent order and attached algos to avoid rejection.

API Integration Patterns

1. Python developers use TradeAPI.place_order() with ordType='trigger' and embed attachAlgoOrds in the request body.

2. WebSocket subscriptions to orders-algo channel deliver real-time status updates including algoId, status, and failCode.

3. Rate limits apply strictly: each API key permits only 20 requests per second, requiring careful batching of multi-instrument strategies.

4. Signature generation follows HMAC-SHA256 over concatenated string of method, path, timestamp, and JSON body.

5. Environment variables store credentials securely, avoiding hard-coded secrets in source files or notebooks.

Frequently Asked Questions

Q1: Can I modify the trigger price of an active stop loss order?No. OKX does not support editing triggered algo orders. Users must cancel and resubmit with updated parameters.

Q2: What happens if both TP and SL prices are hit simultaneously?The exchange processes whichever condition registers first based on microsecond-level timestamp resolution; no guaranteed ordering exists.

Q3: Is it possible to attach more than two algo orders to a single trade?No. The attachAlgoOrds array supports exactly zero, one, or two elements—no extensions beyond this limit are permitted.

Q4: Does the tpOrdKind parameter affect how the take profit executes?Yes. When set to limit, the system places a standard limit order at tpOrdPx. With condition, it waits for tpTriggerPx before submitting.