TRADE scope. You can generate an API key through the One Trading UI.429).client_id, or by instrument_code for the position TP/SL on that instrument. Send exactly one of the two.version as you last read it from Get Exotic Orders (TP/SL) (or from the response that created it). If the TP/SL has changed since, because it fired or another update got there first, the request is refused with VERSION_CONFLICT: read it again and retry.take_profit, stop_loss or both. A level you leave out stays as it is, and null removes it. Removing the last level cancels the TP/SL (TP_SL_REMOVED): the response then carries cancelled: true.TPSL_OUTSIDE_PRICE_BAND.slippage_bps and tpsl_mode cannot be changed: cancel the TP/SL and create it again, or for a position TP/SL create a new one with tpsl_force.TRIGGERED is placing its close and cannot be updated.PENDING next to the ACTIVE one (see Create Order), instrument_code may pick either: use client_id.EXOTIC_ORDER_UPDATED follows on the WebSocket ACCOUNT channel.curl --location --request PATCH 'https://api.onetrading.com/fast/v2/account/exotic-orders' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"instrument_code": "BTC_USD_P",
"version": 2,
"stop_loss": {
"value": "66500",
"type": "MID"
}
}'{
"order": {
"client_id": "0d0b1f0c-7f0e-4f55-9a53-6f6f3c1c2a10",
"instrument_code": "BTC_USD_P",
"order_kind": "TPSL",
"tpsl_mode": "position",
"status": "ACTIVE",
"take_profit": null,
"stop_loss": {
"value": "66500",
"type": "MID"
},
"slippage_bps": 500,
"version": 3,
"side": "BUY",
"market_type": "FUTURES",
"position_id": "1b0f6f5e-2a59-4f0a-9d0e-5f7f3f0f6a11",
"order_id": null,
"type": "MARKET",
"price": null,
"filled_amount": "1.5",
"tp_client_id": "c2a7a1de-6d0b-11f0-8de9-0242ac120002",
"sl_client_id": "1f06d0b6-a7a1-6e20-8de9-0242ac120002",
"created_at": "2026-11-16T10:15:00.000Z",
"filled_at": "2026-11-16T10:15:00.000Z",
"completed_at": null,
"cancelled_at": null
}
}