Request protection with an entry
BTCUSDT on My_API_Key
market long 0.01 sl off 2% tp off 5%The entry requests 0.01 BTC. SL and TP use explicit prefixes; exchange-native protection or separate orders depend on the integration. Read Market for the quantity inherited by inline protection and the limits of risk sizing.
Inspect every result
A filled entry and accepted protection are different outcomes. A protection request can fail after an entry succeeds. Inspect the execution and exchange orders; an alert is not a guarantee of a protected position.
Protect a position that already exists
BTCUSDT on My_API_Key
if posLong continue
sl-or-tp short 100%p sl off e2% tp off e5%Here short means the sell closing side for the long position, and 100%p requests its full size. The entry-relative reference uses the position entry when no market entry preceded it in this block. The SL-or-TP reference explains side selection, hedge mode and native/software handling.
Current-price, entry-relative and absolute levels
Do not assume every offset uses the same reference. A preceding market command can supply the entry reference in the block; without one, standalone entry-relative protection reads the position. Absolute levels need the right side of the market and symbol precision. See StopLoss and TakeProfit before choosing a level.
Partial exits and trailing stops
Several exits need deliberate quantities. Percentages are calculated when orders are placed, not reserved as future percentages of the remaining position. Smart OCO can leave partial exits active until a position condition triggers cleanup; standard OCO responds to primary order events. See the OCO guide and Common Examples.
A fixed stop is not a trailing stop. Trailing Stop has separate activation, callback and supported-futures restrictions. TP-limit can remain unfilled after its trigger. Supported types and cancellation semantics are documented in Exchange Quirks.