Kraken API Unlocked: Running Multi-Strategy Operations on Kraken – Sub-Accounts, API Keys, and the Two Layers of Separation That Matter

TL;DR

• Most multi-strategy operations require two levels of separation: process isolation (one API key per process) and strategic isolation (subaccounts with their own balances, P&L and risk surface). Kraken supports both natively.
• Multiple API keys Fix process issues within a single account: separate nonce sequences, limited permissions, clean blast radius if a single key is compromised.
• Subaccounts Isolate each strategy across linked accounts: separate balances, separate margin calculations, separate per-account rate limits, all while consolidating into a single volume tier for fees.
• Sub-accounts on Kraken Derivatives are open to any eligible customer (set up via a support ticket); on Kraken Spot they are accessible to institutional clients through Kraken’s institutional team.
• Run one API key per process. Most “casual invalid” errors in production are a key shared by multiple processes, not a clock skew issue.

Two levels of separation: process isolation and strategy isolation

The central architectural question for systematic traders is how to separate strategies, permissions and balances between accounts and processes. Kraken offers two distinct responses, operating at different levels.

• Multiple API keys isolate processes and permissions within a single account. Each key has its own occasional sequence, can be extended to specific permissions, and creates clear process boundaries. Balances, volume level, and rate limits per pair remain shared between keys.
• Subaccounts isolate what API keys cannot. Each sub-account on Kraken has its own balances, its own P&L, its own API keys and its own rate limits. The margin is calculated at the sub-account level. A master account links all sub-accounts and, importantly, the transaction volume between linked accounts is consolidated for fee schedule purposes.

What each layer insulates

First layer: API key management for multi-strategy operations

One API key per process

A dynamic robot and a market making robot pointed at the same key will collide at occasional times. The most common casual error in production isn’t clock skew, it’s a key shared between multiple processes, each incrementing the casual independently and scrambling to the API. Split the key, don’t open the occasional window.

The same rule applies to all processes that are not the main trading robot: monitoring dashboards, P&L reconcilers, position flattening scripts, and backtests replaying live data against the REST API each require a dedicated key. When a key generates an error or hits a rate limit, you immediately know which process to investigate.

Minimum permissions per role

Kraken API keys are fully extended. A read-only dashboard does not need ordering permissions. A reconciliation job extracting exchange history never requires withdrawal authorization.

Extend each key to exactly what its process requires and nothing more. The cost is one minute when creating the key.

For the full set of best practices (including permission scopes, 2FA keys, expiration, rotation, and per-key controls), see Kraken’s API Key Security Guide and the How to Create an API Key documentation.

Second layer: sub-accounts on Kraken

Subaccounts provide two structural advantages for multi-strategy operations:

• Transaction volume on linked accounts is aggregated for Price list volumes floor.
• Movement of funds instantly and free of charge between the main account and the sub-accounts.

The canonical use case is to manage a market making book and a directional book in parallel without mixing exposure. Separate mandates, separate volatility profiles or hedging portfolio against a directional position; each operates within its own risk surface, preventing the withdrawal of one strategy from affecting the margin or liquidation threshold of another.

How to create a Kraken sub-account (Derivatives and Spot)

Kraken Derivatives is open to any eligible customer. Sub-account creation is done through the Kraken support team:

1. Create a new Kraken account for the subaccount and verify it.
2. Unlock derivatives trading from the sub-account.
3. Submit a Kraken Derivatives support ticket from the primary account email address requesting that the accounts be linked.

Once linked, sub-account management (listing, balance retrieval and transfers between main accounts and sub-accounts or between margin accounts sharing a collateral currency) is done via the Futures REST API.

Kraken Spot is only institutional. The REST API documents a CreateSubaccount endpoint, but availability is limited. CreateSubaccount must be called using an API key from the master account, and the endpoint requires the Withdraw funds authorization on this master key. Spot sub-accounts are reserved for institutional clients. Access this area via your Kraken relationship manager.

Kraken subaccount operational caveats

• Withdrawals from sub-accounts are blocked. Funds must be transferred back to the main account before you can exit Kraken Derivatives. Integrate this into reconciliation and treasury workflows from the start.
• API keys are generated and controlled separately on each sub-account. The main account does not have subaccount keys.
• API rate limits are managed separately per account.
• Connections are separate for each sub-account.
• Temporary blockages last approximately 15 minutes. They trigger after too many failed API calls, occasional invalid errors, or invalid signatures in a short period of time. A misconfigured key in a tight retry loop can keep a policy offline for almost an hour.

Getting started: API keys and subaccounts

1. Audit current keys. What is each one for, what permissions it has, if IP restriction is enabled.
2. Divide keys by process. One key per process, minimum permissions.
3. Apply allowed IP address lists at each production key.
4. Test in UAT before promoting any new key configuration to production.
5. Choose subaccounts. Multiple keys are enough if the strategies share capital. Subaccounts are necessary when strategies require separate capital, P&L, or risk. Derived via support ticket, Spot via your Kraken relationship manager.

Create an API key, or for institutional subaccount setup and FIX access, contact the Kraken Institutional team.

FAQs

Who can use subaccounts on Kraken?
Sub-accounts on Kraken Derivatives are available to any eligible customer and are created via a support ticket. Sub-accounts on Kraken Spot are currently available to institutional clients through Kraken’s Institutional Onboarding team.

What is the difference between API keys and subaccounts on Kraken?
API keys isolate processes and permissions within a single Kraken account. Each key has its own nonce sequence and broad permissions, but shares balances and charge limits. Subaccounts are separate linked accounts, each with independent balances, margin, rate limits, and API keys, while consolidating trading volume into a single fee tier.

Can I withdraw directly from a Kraken Derivatives subaccount?
Funds must be transferred back to the main account before you can exit Kraken Derivatives.

Do sub-accounts on Kraken share trading fees between linked accounts?
Yes. Trading volume across all linked subaccounts is consolidated into a single fee schedule volume tier, meaning your combined activity across strategies contributes to lower fee rates.