Limit command

What it does

limit places a limit order.

You can drive the limit price from:

offset
price

Use TradingView Order Syntax first if you need the full command structure before working through individual command types.

Minimal syntax

ALPHA(BTCUSDT){type=limit,side=buy,amount=0.001,offset=-1%}

Typical fields

type=limit
side=buy or side=sell
amount=...
position=...
offset=...
price=...
reduceOnly=true
postOnly=true
tp=...
sl=...
tag=...

Buy below market

ALPHA(BTCUSDT){type=limit,side=buy,amount=0.001,offset=-1%}

Sell above market

ALPHA(BTCUSDT){type=limit,side=sell,amount=0.001,offset=1%}

Use an absolute price

ALPHA(BTCUSDT){type=limit,side=buy,amount=0.001,offset=@68000}

or:

ALPHA(BTCUSDT){type=limit,side=buy,amount=0.001,price=@68000}

Reduce-only limit exit

ALPHA(BTCUSDT){type=limit,position=0,offset=1%,reduceOnly=true}

Limit with TP and SL

ALPHA(BTCUSDT){type=limit,side=buy,amount=0.001,offset=-1%,tp=1%,sl=0.5%}

About `postOnly`

If you do not specify postOnly, the current execution flow defaults limit orders toward post-only behavior in the common limit path.

If you want to be explicit, set it yourself:

postOnly=true

Offset vs price

`offset=...`

Relative to current or reference price.

Examples:

offset=1%
offset=-1%
offset=@68000
offset=e1%

`price=...`

Explicit order price or price token.

Examples:

price=@68000
price=1%
price=e1%

Common mistakes

Invalid offset

If the offset cannot resolve into a valid price, the command is skipped.

Post-only on a crossing price

A post-only order can be rejected if it would take liquidity immediately.

Using `position=0` without `reduceOnly=true`

For exit-style workflows, that can produce the wrong order semantics.