Kraken oto=: attach one exit to your entry
On Kraken, a buy with fsl= does not buy. Autoview reads the stop as an exit for a position you already hold, so it places a sell stop instead. If you want the buy to go in with its stop already attached, add oto=1.
This page comes from the Autoview integrations code that runs on our servers today and its tests. We read the code; we did not place live Kraken orders for this guide.
With and without oto=
| Alert | What Autoview sends to Kraken |
|---|---|
e=kraken s=XBTUSD b=buy q=0.01 t=market fsl=59000 | A sell stop-loss at 59000. No buy. |
e=kraken s=XBTUSD b=buy q=0.01 t=market fsl=59000 oto=1 | A market buy, with a stop-loss at 59000 attached as Kraken's conditional close. |
The exit travels on the entry order as Kraken's conditional close, so you send one alert instead of two.
Pick one exit
Kraken's conditional close holds a single order. Put exactly one of these on the line with oto=1:
- A stop loss,
sl=orfsl=. - A take profit,
tp=orftp=. - A trailing stop,
ts=orfts=. It is attached as a Kraken trailing stop at that distance.
Autoview refuses the line before it reaches Kraken when:
- it has both a stop loss and a take profit,
- it has a trailing stop together with a stop loss or take profit,
- it has
oto=1and no stop loss, take profit or trailing stop at all.
If you need a stop and a target on the same Kraken position, send the entry with one of them attached, and send the other as its own order.
Market entry or limit entry
A stop loss is the same on every entry type. A take profit depends on the entry type:
- Stop loss, any entry. The exit is a plain stop-loss at your price. Market, limit and post-only entries all get the same kind of stop: when price reaches it, Kraken closes at market.
- Take profit, market entry. The exit is a plain take-profit at your price.
- Take profit, limit entry. The exit is a take-profit-limit. Your
tp=orftp=is the trigger, and the entry's limit price is used as the exit's limit price.
e=kraken s=XBTUSD b=buy q=0.01 t=limit fp=60800 fsl=59000 oto=1 d=1That line logs a limit buy at 60800 with a stop-loss at 59000 attached. If price falls to 59000 after the buy fills, the stop sells at market. Nothing is sent while d=1 is on the line.
e=kraken s=XBTUSD b=buy q=0.01 t=limit fp=60800 ftp=61000 oto=1 d=1That line logs a limit buy at 60800 with a take-profit-limit attached: it triggers at 61000, with 60800 as its limit price.
Earlier, a stop loss on a limit entry was sent as a stop-loss-limit with your entry price as its limit. On a buy, that left the exit waiting above the market after the stop triggered, so it did not close the position. Autoview now sends a plain stop-loss instead. An order you placed before the change keeps the form it was placed with, so check your open Kraken orders if you used oto=1 with a stop on a limit entry.
A relative sl= or tp= is measured from price= when you send one, and from Kraken's current bid or ask when you do not. It is not measured from your fill, which Autoview does not know yet. Use fsl= and ftp= when you want exact prices.
px= wins over oto=
px= and fpx= turn the entry into a stop entry, and Autoview checks them first. A line with px= and oto=1 goes out as the stop entry with nothing attached, and the stop loss, take profit or trailing stop on it is dropped. Leave px= off a line that uses oto=1.
Which connections read oto=
Kraken spot (e=kraken) and Alpaca. Kraken Futures does not read it. On Alpaca, oto=1 builds an Alpaca OTO order; see Alpaca bracket orders.
For the rest of Kraken's keys, including the side rule for fpx= and fsl=, see the Kraken command reference.