Does Bybit attach a stop-loss and take-profit to the same order in Autoview?

Yes. Adding fsl= or ftp= to an entry order attaches the protective stop or target directly to that position, keeping the same side rather than opening a separate order. This is the opposite of Kraken, where fsl= and ftp= resolve as closing orders on the flipped side.

Can I place a trailing stop or a conditional entry on Bybit through Autoview?

Yes to both. fts= sets a trailing-stop distance that follows the market, and fpx= arms a conditional entry that waits until price reaches a trigger before it places, keeping your original side. Both apply on top of a market or limit order on the perpetual surface.

How do I set leverage or close a position on Bybit perpetuals with Autoview?

Add l= to any order to set the position's leverage, for example l=5 for 5x; Bybit applies it through a separate call rather than showing it on the order itself. To close, send c=position to flatten the position or c=order to cancel resting orders; Bybit has no c=all.

What happens if I don't set a quantity on a Bybit order in Autoview?

Leaving q= off commits 100% of your available balance to the order, on either side. q= also accepts a plain coin amount, a percentage like q=50%, or a notional value in the quote currency with u=currency. Set a deliberate size on every order rather than relying on the default.

Bybit perpetuals command cheat sheet

Autoview · Guide · Updated July 11, 2026

This page lists the Bybit perpetual orders you can place from an Autoview alert, with a copy-ready command for each. It assumes you already know the shape of an Autoview command. If you don't, read the command reference first. For the full parameter-by-parameter detail behind these lines, see the Bybit perpetuals command reference. Trading spot instead? Use the Bybit spot cheat sheet.

Every command below was run through Autoview's parser in dry-run mode (d=1) against Bybit's real order-parameter schema, and the resolved order shown is what the parser produced, not hand-typed. That confirms the field mapping against Bybit's documented order schema; it does not mean these commands were submitted as live orders on an exchange account, so run your own first order with d=1 and read the result before trading real size.

Name the symbol and route

s= is the symbol, written as one word with no separator: s=BTCUSDT is the USDT linear perpetual. e=BYBIT sends the order to the perpetual side of your connected Bybit account. Every example below starts with both. That routing is a Chrome extension behavior, code-verified 2026-07-29: the extension reads e= to pick the connected broker. On the webhook platform the exchange is already fixed to the webhook itself, so e= is accepted there but never consulted -- harmless to include, but it isn't what's routing the order.

The order types

Pick a row, copy the command, change the symbol and size to yours. t= sets the order type and defaults to limit, so a market order sets it explicitly.

Order	Command
Market buy	`e=BYBIT s=BTCUSDT b=buy t=market q=0.001`
Market sell	`e=BYBIT s=BTCUSDT b=sell t=market q=0.001`
Limit	`e=BYBIT s=BTCUSDT b=buy t=limit fp=60000 q=0.001`
Immediate or cancel	`e=BYBIT s=BTCUSDT b=buy t=ioc fp=60000 q=0.001`
Fill or kill	`e=BYBIT s=BTCUSDT b=buy t=fok fp=60000 q=0.001`
Post-only (maker)	`e=BYBIT s=BTCUSDT b=buy t=post fp=60000 q=0.001`

fp= is the fixed limit price a limit order rests at; a market order takes no price, so leave it off. t=ioc fills what it can at once and cancels the rest; t=fok fills in full or not at all; t=post joins the book as a maker and is rejected rather than crossing the spread.

The one-order bracket

This is the Bybit feature worth learning. A stop-loss and a take-profit ride along on the entry order itself, on the same order, with the side unchanged. One command opens the position and arms both protections.

Order	Command
Buy with attached stop	`e=BYBIT s=BTCUSDT b=buy t=market fsl=50000 q=0.001`
Buy with attached target	`e=BYBIT s=BTCUSDT b=buy t=market ftp=70000 q=0.001`
Buy with both (full bracket)	`e=BYBIT s=BTCUSDT b=buy t=market fsl=50000 ftp=70000 q=0.001`

On Bybit the bracket stays on your side; it does not flip. If you have used Kraken, that is the opposite of what you know, where the same fsl= and ftp= become separate orders on the other side. Run a new bracket with d=1 once to see the resolved order before you trust it live.

Conditional, trailing, and leverage

Order	Command
Conditional entry (arms at a trigger)	`e=BYBIT s=BTCUSDT b=buy t=market fpx=70000 q=0.001`
Trailing stop (distance behind price)	`e=BYBIT s=BTCUSDT b=buy t=market fts=500 q=0.001`
Set leverage on the order	`e=BYBIT s=BTCUSDT b=buy t=market q=0.001 l=5`

fpx= holds the order until the price reaches the trigger, keeping your side. fts= sets a trailing-stop distance. l=5 sets the position to 5x; Bybit applies it through a separate call, so it governs the position rather than showing on the order. The full reference covers the trigger price source, activation price, hedge mode, and reduce-only.

Size in coins

q= is the quantity, in the base coin (the BTC in BTCUSDT).

q=0.001 is 0.001 BTC.
q=50% uses half your available balance, sized at fill time.
q=100 u=currency commits about 100 USDT, converted to the base quantity at the current price.

Leave q= off and Autoview uses 100% of the balance. Set the size you mean on every order. This is the cheapest mistake to avoid and the easiest one to make.

Closing out

Cancel resting orders with c=order, and close an open position with c=position.

e=BYBIT s=BTCUSDT c=position

There is no c=all on Bybit. Cancel orders with c=order and close the position with c=position.

Test before you go live

Append d=1 to any command and Autoview parses it, reports what it would have done, and places nothing:

e=BYBIT s=BTCUSDT b=buy t=market q=0.001 d=1

Read the log, confirm the symbol, side, and size are what you meant, then drop d=1 and let it fill. For more on reading the log, see test and debug your setup.

Full Bybit command reference