stop / stop-limit - Conditional Entry Orders

Enter positions when price breaks through key levels. Perfect for breakout and momentum strategies.

What is stop?

stop places a conditional order that ENTERS a position when price crosses a specified level. This is perfect for breakout strategies - entering when price confirms a move beyond resistance or support.

Breakout Long
stop long 0.01 @ 51000 - Buy when price rises above $51,000 (breaking resistance)
Breakout Short
stop short 0.01 @ 49000 - Sell when price falls below $49,000 (breaking support)

NOT for Stop Loss Protection!

The stop command is for ENTERING positions on breakouts, not for protection.

For stop loss and take profit protection, use the inline properties sl and tp with commands like market or limit:
Example: market long 0.01 sl off 2% tp off 5%

Syntax

// Stop-Market (triggers at price, executes at market)
stop long|short <amount> @ <price>
stop long|short <amount> off <value>

// Stop-Limit (triggers at price, places limit order)
stop-limit long|short <amount> off <trigger_value> off <limit_offset>

// With optional tag
stop long|short <amount> @ <price> #tag

Direction: Use long to buy on upward breakout, short to sell on downward breakout.

Parameters

long|shortRequired

Type: keyword | Values: long (or buy), short (or sell)

Direction to enter. long buys on upward breakout, short sells on downward breakout.

amountRequired

Type: number or string

Size of position to enter. Can specify:

Format	Example	Meaning
`number`	`0.01`	0.01 BTC (absolute amount)
`%`	`50%`	50% of available balance

@ price / off valueRequired

Type: number or string

Where to trigger the breakout entry:

@ 51000 - Absolute price of $51,000 (most common for breakouts)
off 100 - $100 above/below current price
off 2% - 2% above/below current price

For breakouts, absolute prices (@ 51000) are most common since you're targeting specific resistance/support levels.

#tagOptional

Type: tag identifier

Label this order for later reference. Use #tag syntax. Useful for canceling specific breakout orders with rem #tag.

Real-World Examples

1. Upward Breakout - Buy Above Resistance

Enter long when BTC breaks above $51,000 resistance.

BTCUSDT on My_API_Key
// Wait for breakout above resistance
stop long 0.01 @ 51000

Order triggers when price rises above $51,000. Perfect for entering confirmed uptrends.

2. Downward Breakout - Sell Below Support

Enter short when ETH breaks below $3,000 support.

ETHUSDT on My_API_Key
// Wait for breakdown below support
stop short 0.5 @ 3000

Order triggers when price falls below $3,000. Catches downward momentum trades.

3. Multiple Breakout Levels with Tags

Place breakout entries at 3 different resistance levels, cancel others when one fills.

BTCUSDT on My_API_Key
// Three resistance levels to watch
stop long 0.01 @ 50000 #breakout
stop long 0.01 @ 51000 #breakout
stop long 0.01 @ 52000 #breakout
// Cancel others when one fills
oco #breakout

As soon as any resistance breaks, that order fills and the others are cancelled automatically.

4. Breakout with Immediate Protection

Enter on breakout, then immediately add stop loss and take profit protection.

BTCUSDT on My_API_Key
// Enter on upward breakout
stop long 0.01 @ 51000
// Add protection after entry (in separate webhook)
sl-or-tp short 100%p sl off 2% tp off 5%

First webhook places breakout entry. Second webhook (triggered after fill) adds protection.

5. Percentage-Based Breakout

Enter when price moves 3% above current level.

ETHUSDT on My_API_Key
// Enter if price rallies 3%
stop long 0.3 off 3%

Triggers when price is 3% above current price. Useful for catching momentum moves without targeting specific levels.

6. Stop-Limit Order (Advanced)

Trigger 2% above the reference price, then place a buy limit 0.5% below that trigger.

BTCUSDT on My_API_Key
// With no position: trigger 2% above current
// Buy limit 0.5% below the trigger
stop-limit long 0.01 off 2% off 0.5%

With a reference price of 100, the trigger is 102 and the buy limit is 101.49 before exchange rounding. The first reference is the position entry when available, otherwise current price; this example assumes no existing position. The second offset uses the trigger as its reference. The order can remain unfilled after activation if price does not return to the limit.

Key Points About Breakout Orders

Use @ price for specific resistance/support levels
Use off % for dynamic breakouts based on current price
Combine with oco when placing multiple breakout levels
Add protection in a separate webhook triggered after entry fills

Best Practices

Use absolute prices for key levels - Specific resistance/support levels are more reliable than percentages
Always add protection - Use sl-or-tp in a follow-up webhook after breakout entry fills
Use tags for complex setups - Tag related breakout orders to manage them as a group with oco
Consider false breakouts - Price may temporarily cross a level then reverse. Plan your risk accordingly.

Exchange-Specific Behavior

Stop order implementation varies by exchange:

Exchange	Stop-Market	Stop-Limit	Notes
Binance	Yes	Yes	STOP_MARKET and STOP orders
ByBit	Yes	Yes	Native conditional orders
Bitget	Yes	Limited	Plan orders API
HTX V5 Futures	Yes	Yes	Entry trigger orders use last price only; an explicit limit price selects stop-limit.
WEEX Futures	Yes	Yes	Conditional orders with last or mark price; index is unsupported.
Bitunix	Yes	No	Native stop orders
KuCoin	Yes	Yes	Stop orders API

Stop-Limit note: Support depends on the exchange and market. Confirm that the returned order includes the intended trigger and limit prices; activation does not guarantee a fill. These futures notes do not establish spot support.

Related Commands

sl-or-tp

- Add stop loss + take profit protection after breakout entry

oco

- Monitor multiple breakout levels, cancel others when one fills

rem

- Cancel breakout orders manually

limit

- Place entry orders at specific prices (no trigger required)