Kraken API Unlocked: working multi-strategy operations on Kraken — subaccounts, API keys, and the 2 layers of separation that matter

TL;DR

• Most multi-strategy operations want two layers of separation: course of isolation (one API key per course of) and technique isolation (subaccounts with their very own balances, P&L, and threat floor). Kraken helps each natively.
• A number of API keys resolve course of issues inside one account: separate nonce sequences, scoped permissions, clear blast radius if a single secret’s compromised.
• Subaccounts isolate every technique throughout linked accounts: separate balances, separate margin calculations, separate per-account price limits, whereas nonetheless consolidating into one quantity tier for charges.
• Subaccounts on Kraken Derivatives are open to any eligible consumer (arrange by way of assist ticket); on Kraken Spot they’re gated to institutional purchasers by way of the Kraken institutional workforce.
• Run one API key per course of. Most “invalid nonce” errors in manufacturing are one key shared throughout a number of processes, not a clock-skew drawback.

Two layers of separation: course of isolation vs. technique isolation

The core architectural query for systematic merchants is the right way to separate methods, permissions, and balances throughout accounts and processes. Kraken supplies two distinct solutions, working at completely different layers.

• A number of API keys isolate processes and permissions inside one account. Every key carries its personal nonce sequence, might be scoped to particular permissions, and creates clear course of boundaries. Balances, quantity tier, and per-pair price limits stay shared throughout keys.
• Subaccounts isolate what API keys can not. Every subaccount on Kraken has its personal balances, its personal P&L, its personal API keys, and its personal price limits. Margin is calculated on the subaccount stage. A grasp account hyperlinks all subaccounts — and crucially, buying and selling quantity throughout linked accounts is consolidated for payment schedule tier functions.

What every layer isolates

Layer one: API key administration for multi-strategy operations

One API key per course of

A momentum bot and a market-making bot pointed on the similar key will collide on nonces. The commonest nonce error in manufacturing isn’t clock skew, it’s one key shared throughout a number of processes, every incrementing the nonce independently and racing one another to the API. Cut up the important thing, don’t elevate the nonce window.

The identical rule applies to each course of that isn’t the first buying and selling bot: monitoring dashboards, P&L reconcilers, position-flattening scripts, and backtests replaying stay knowledge towards the REST API every want a devoted key. When a key throws an error or hits a price restrict, you instantly know which course of to analyze.

Minimal permissions per function

Kraken API keys are totally scoped. A read-only dashboard doesn’t want order placement permissions. A reconciliation job pulling commerce historical past doesn’t want withdrawal permissions, ever.

Scope every key to precisely what its course of requires and nothing extra. The associated fee is one minute throughout key creation. 

For the total set of greatest practices (together with permission scopes, key 2FA, expiration, rotation, and per-key controls) see Kraken’s API Key Safety information and Methods to create an API key documentation.

Layer two: subaccounts on Kraken

Subaccounts ship two structural benefits for multi-strategy operations:

• Buying and selling quantity throughout linked accounts is grouped for the Price Schedule Volumes tier.
• Funds transfer immediately and fee-free between the grasp account and subaccounts.

The canonical use case is working a market-making e book and a directional e book in parallel with out commingling publicity. Separate mandates, separate volatility profiles, or a hedging e book towards a directional place; every operates inside its personal threat floor, stopping one technique’s drawdown from affecting one other’s margin or liquidation threshold.

Methods to create a Kraken subaccount (Derivatives and Spot)

Kraken Derivatives is open to any eligible consumer. Subaccount creation goes by way of the Kraken assist workforce:

1. Create a brand new Kraken account for the subaccount and confirm it.
2. Unlock Derivatives buying and selling from the subaccount.
3. Submit a Kraken Derivatives assist ticket from the grasp account e-mail deal with requesting that the accounts be linked.

As soon as linked, subaccount administration (itemizing, steadiness retrieval, and transfers between grasp and subaccounts or between margin accounts sharing a collateral foreign money) runs by way of the Futures REST API.

Kraken Spot is institutional-only. The REST API paperwork a CreateSubaccount endpoint, however availability is gated. CreateSubaccount have to be known as utilizing an API key from the grasp account, and the endpoint requires the Withdraw Funds permission on that grasp key. Spot subaccounts are restricted to institutional purchasers. Attain this floor by way of your Kraken relationship supervisor.

Kraken subaccount operational caveats

• Withdrawals from subaccounts are blocked. Funds need to be moved again to the grasp account earlier than they will go away Kraken Derivatives. Construct that into reconciliation and treasury workflows from the beginning.
• API keys are generated and managed individually on every subaccount. The grasp account doesn’t personal subaccount keys.
• API price limits are managed individually per account.
• Signal-ins are separate for every subaccount.
• Short-term lockouts final about quarter-hour. They set off after too many failed API calls, invalid nonce errors, or invalid signatures in a brief interval. A misconfigured key in a good retry loop can maintain a technique offline for the higher a part of an hour.

Getting began: API keys and subaccounts

1. Audit present keys. What every one is used for, what permissions it has, whether or not IP restriction is on.
2. Cut up keys by course of. One key per course of, minimal permissions.
3. Apply IP allowlists to each manufacturing key.
4. Check in UAT earlier than selling any new key configuration to manufacturing.
5. Determine on subaccounts. A number of keys are sufficient if methods share capital. Subaccounts are wanted when methods want separate capital, P&L, or threat. Derivatives by way of assist ticket, Spot by way of your Kraken relationship supervisor.

Create an API key, or for institutional subaccount setups and FIX entry, contact the Kraken Institutional workforce.

FAQ

Who can use subaccounts on Kraken?
Subaccounts on Kraken Derivatives can be found to any eligible consumer and are arrange by way of a assist ticket. Subaccounts on Kraken Spot are at the moment accessible to institutional purchasers by way of the Kraken institutional onboarding workforce.

What’s the distinction between API keys and subaccounts on Kraken?
API keys isolate processes and permissions inside a single Kraken account. Every key has its personal nonce sequence and scoped permissions, however shares balances and price limits. Subaccounts are separate linked accounts, every with unbiased balances, margin, price limits, and API keys, whereas nonetheless consolidating buying and selling quantity into one payment tier.

Can I withdraw immediately from a Kraken Derivatives subaccount?
No. Funds need to be moved again to the grasp account earlier than they will go away Kraken Derivatives.

Do subaccounts on Kraken share buying and selling charges throughout linked accounts?
Sure. Buying and selling quantity throughout all linked subaccounts is consolidated right into a single payment schedule quantity tier, that means your mixed exercise throughout methods contributes to decrease payment charges.