OCO Orders via TradingView Webhook: Native Protection, Standard OCO and Smart OCO

Three different protection mechanisms

Native exchange protection, standard OCO and Smart OCO serve different purposes. A stop loss or take profit accepted by an exchange follows that exchange’s rules. Native linkage, where supported, is managed there. Flipr.Cloud’s software monitor is a separate service; it cannot make order placement and cancellation atomic.

Standard OCO watches a group of existing orders. When a primary tracked order is no longer open, including cancellation, the monitor requests cancellation of the remaining group. Dependent protections in hierarchical groups do not trigger the same cleanup. See the OCO reference.

Smart OCO follows the position

Smart OCO requests cleanup when the monitored position closes or flips side, according to its settings. A partial exit does not by itself cancel the remaining ladder. It monitors orders already present; it does not create SL/TP orders. See Smart OCO explained and the command options.

BTCUSDT on My_API_Key
if posLong continue
stoploss off e2%
limit short 50%p off e3% reduce #exit1
limit short 50%p off e6% reduce #exit2
smart-oco sell

The two limit quantities are calculated when placed. They sum to the position only if its size stays unchanged during placement, before rounding. Reduce-only support and trigger behaviour depend on the market. An accepted limit can execute immediately if it crosses the market.

A combined SL/TP request

BTCUSDT on My_API_Key
market long 0.01
sl-or-tp short 100%p sl off 2% tp off 5%

sl-or-tp creates protections using the supported native or software path. Here short selects the sell closing side for a long position. Inspect the entry and both protection results; commands can fail independently and execution can continue after an error. Pending limit entries require exchange-specific protection handling, not an assumption that protection is active immediately.

Timing, replacement and compatibility

Sending another stoploss or takeprofit command does not universally replace the previous order or preserve an old group. Inspect the open orders and choose an explicit cancellation and replacement sequence. reset-oco stops software monitoring; it does not cancel exchange orders.

Consult Exchange Quirks for native TP/SL visibility, tag and cancellation limits, and supported Demo/Testnet environments. Header names are saved API key labels, not exchange-routing suffixes.