How to Automate Kraken Spot Trading with Cornix

Table of contents

• Plan your first Kraken Spot bot
• Create a Kraken key that can trade but cannot withdraw
• Choose one bot for the instruction you already understand
• Check the full cost and exposure of a Spot trade
• Test the path, then monitor the exchange account

A Kraken Spot trading bot can execute a rule on your exchange account without requiring you to place every order manually. To automate Kraken Spot trading with Cornix, create a restricted Kraken API key, connect it to Cornix, and test one strategy with a defined spending limit.

Cornix supports Kraken Spot (supported exchanges), and you can automate it with our DCA, Grid, Signals, or TradingView bots. That gives you several ways to supply a trade instruction.

Plan your first Kraken Spot bot

Start with the market you actually want to trade, and check that your planned order size meets that pair's minimum on Kraken.

Decide who supplies the instruction. If you have a repeatable plan for adding to a position, examine DCA. If your thesis depends on price moving within a chosen range, examine Grid. If you follow a channel, assess its signals and your own allocation rules. If you have a specific chart condition, examine an alert-driven TradingView bot. Each is a separate starting path in Cornix (getting started). Choosing among them is a strategy decision, not a step that the API connection makes for you.

For a first live run, write down the pair, maximum amount you are willing to commit, entry trigger, intended exit, and condition that would make you pause. A rule such as “buy whenever the market looks promising” still calls for a human decision. A rule you can describe precisely is easier to configure, test, and audit after an unexpected order.

Create a Kraken key that can trade but cannot withdraw

Here's the connection sequence, which is also in our Kraken Spot API-key guide. Sign in to Kraken Pro, open Settings, go to Connections & API, and choose Create API key. Give this key a recognizable name dedicated to Cornix. Under Fund Permissions, enable Query. Under Orders and trades, enable Query open orders & trades, Query closed orders & trades, Create & modify orders, and Cancel & close orders. These permissions allow the connected workflow to read balances and order history, place or change trades, and cancel orders.

Leave withdrawal permission off. Trading authority is meaningful access to your account, even without withdrawal authority, so do not add permissions simply because they are available. Kraken's API-key security guidance explains that an API key can authorize sensitive actions according to its settings. Secure your Kraken and Cornix logins, keep the private key out of messages and screenshots, and revoke a key you no longer use. If you share a setup image for help, crop or redact both the API key and private key before sending it.

Before generating the key, open Cornix Accounts, select +Create, and choose Kraken. Copy the unique IP addresses Cornix displays for your connection into Kraken's IP address restriction field. Do not substitute your home IP: the restriction must permit the IPs Cornix supplies for its connection. Generate the key and complete Kraken's verification, then copy the API key and private key into the Kraken account form in Cornix. Keep the key pair private while moving between the two screens.

If the connection fails, check the copied IP list and credentials before broadening permissions. A key missing the required order or balance permission can also interrupt a third-party trading workflow; Kraken explains this in its third-party API troubleshooting guide. Review the settings deliberately rather than removing IP restrictions or enabling withdrawal access to make an error disappear.

Choose one bot for the instruction you already understand

DCA: Our DCA bot buys in stages under rules you set. Consider it when you have decided in advance how additional entries will be funded and when the sequence ends. Calculate the combined cost of every possible entry, not just the first buy. If a falling market can trigger more purchases than you can comfortably fund, reduce the order amounts or number of entries before activation.

Grid: Our Grid bot places a series of orders across a price range you choose. Consider it when your trading idea depends on repeated movement within that range. Decide what you will do if price moves beyond it and stays there. A bot can keep following its configured levels, but it cannot decide whether your original range thesis is still sound. Check both the total funds committed to orders and what asset balance you could hold after they execute.

Signals: Our Signals Bot acts on instructions from a supported signal source, using settings you control (getting started). Its suitability therefore depends on two separate judgments: whether the signal source deserves your trust and whether your own sizing and exit rules fit the account. Do not equate someone else's published entry with permission to put an unlimited portion of your Kraken balance at risk. Start with a single source whose trade format and loss handling you can inspect.

TradingView: Our TradingView bot turns your chart alerts into orders using the bot's settings. Use this route when an alert expresses a sufficiently precise action, rather than merely reminding you to review the chart. Check what a repeated alert would do, which account and symbol the bot would address, and how to pause it. If a chart condition still needs your judgment about context or liquidity, keep the alert informational instead of routing it directly to execution.

None of these four paths is automatically the best Kraken trading bot for every trader. DCA can increase committed capital as entries accumulate; a Grid depends on its range; Signals depend on the instruction source; and TradingView automation depends on the alert and bot settings agreeing. Pick the input you can explain and supervise. When you create the bot, select your Kraken account and the Spot pair you planned, then check the bot's order summary to confirm it will trade that pair the way you intend before you activate it. For a broader discussion of turning rules into orders, the crypto trading automation guide explores what should be automated and what should remain under review.

Check the full cost and exposure of a Spot trade

Before sizing the first order, look at the pair's current order requirements and the funds available in your Kraken account. Count all planned bot entries and open orders against one spending cap. If two bots could trade the same asset, count their possible commitments together. An amount that looks modest for a single order may become a much larger position after several fills.

Kraken's Spot trading fee schedule publishes Spot maker and taker rates that depend on the applicable tier and trading conditions. Review the fee schedule and your account's rate rather than assuming a bot uses one fixed fee. A strategy that enters and exits frequently must clear trading costs before it produces a net gain. Also consider the spread and possible slippage: an order may execute at a less favorable price than the one used in your calculation, especially when the market moves quickly or available liquidity is thin.

Check the minimum order and size increment for the specific pair you intend to automate in Kraken before setting bot amounts. A total budget can be adequate while an individual Grid order or DCA entry is too small for the market's rules. Conversely, increasing every order merely to clear a minimum may exceed your planned exposure. Resolve that conflict by changing the strategy or choosing a suitable pair, not by silently raising the risk budget.

Keep the first deployment narrow: one Spot pair, one bot, and a maximum loss or pause condition you can act on. Automation handles repeated instructions; it does not make a price forecast reliable. Neither a successful backtest nor a completed API setup guarantees returns, fills at a chosen price, or protection from a sharp move.

Test the path, then monitor the exchange account

Our demo accounts let you run simulated Signals, DCA, Grid, and TradingView bots without an exchange API key. Use a demo to rehearse the configuration: check the selected symbol, entry amount, subsequent orders, exits, alert or signal behavior, and the control you would use to stop the bot. Simulation catches setup mistakes, but it can't show how a live Kraken order will fill.

When you move to a small live Spot trade, verify what happened in both places. Review the bot's status and orders in Cornix, then check the actual orders, balances, and fills on Kraken. If an order is rejected, partially filled, or different from what you intended, pause before repeating the trigger. Inspect the pair's minimums, available balance, permissions, IP restriction, and configuration rather than assuming the next attempt will fix itself.

Establish a short monitoring routine that matches the bot's activity. Check open orders, the amount already spent, remaining buying capacity, fees, and whether the reason for the trade still holds. Know how to deactivate the bot and how to revoke its Kraken key if the connection should no longer have authority. Revoking a key is a credential control; it does not substitute for reviewing any position or order already open at the exchange.

Automate Kraken Spot once the key has restricted trading permissions and the bot's full capital commitment and stop procedure are clear. Start with one rule you can test and monitor rather than several bots you cannot easily disentangle. When those controls are in place, connect Kraken Spot to Cornix.

Frequently Asked Questions

Which Kraken API permissions does Cornix need?

Our Kraken Spot API-key guide lists Fund Permissions: Query, plus query open and closed orders and trades, create and modify orders, and cancel and close orders. It also explains how to apply the Cornix-provided IP restriction. Leave withdrawal permission disabled.

Can I test a bot before trading on Kraken?

Yes. Our demo accounts let you rehearse Signals, DCA, Grid, or TradingView configurations without connecting an exchange API key. A simulation checks setup behavior, not future profits or live fills.