Support & frequently asked questions

On Kraken open Settings, then API, then Create key. Enable querying balances and creating or cancelling orders. Leave every withdrawal permission switched off. Copy the key and the secret — the secret is shown only once — and paste both into the Exchange keys screen of the terminal.

All withdrawal and funding permissions. The terminal never needs them, and disabling them means no one can move coins or cash out of your exchange account, whatever happens to the key.

Secrets are encrypted before they are written to the database and are decrypted only inside the server process that signs a request for your own account. They are never shown again in the interface and never sent to your browser.

Kraken has no separate practice network. In test mode the terminal signs a genuine order and sends it to your own Kraken account in validation mode: Kraken checks the pair, permissions, size, precision and funds, then discards it. Nothing is executed and no money moves.

Yes. Delete the connection in the Exchange keys screen, and revoke the key inside your exchange account as well. Automation stops immediately for that exchange.

The key was mistyped, has been revoked, or lacks the trading permission. Create a new key with balance and order permissions, withdrawals off, and reconnect it.

The requested size is below the exchange minimum or has too many decimals for that pair. Increase the amount for that asset in Allocations, or verify with a slightly larger test volume.

Your account balance in the quote currency cannot cover the order. Fund the account or lower the allocated amount for that asset. This reply still proves the signing and routing path works.

The same key is being used by another tool at the same time, or the key's nonce window is too small. Use a dedicated key for the terminal and retry.

The exchange did not answer within fifteen seconds, usually during a market-wide spike. The attempt is recorded as failed and nothing is executed; simply run it again.

Each cycle is recorded with the number of positions evaluated, executed and skipped, its duration, and whether it finished or failed. A steady stream of finished cycles with a recent timestamp means the engine is healthy.

Either you paused it, or a safety limit was reached — for example the maximum daily loss or the maximum total allocation. The reason is shown next to the switch; adjust the limit or re-enable it when you are ready.

It is the share of engine cycles in the last thirty days that finished without an error. It measures how the software executes, not market accuracy or profit.

The conditions for a transition were not met, the allocation is inactive, or a safety limit blocked it. Skipping is normal and expected on most cycles.

No. Your coins and cash stay in your own exchange account at all times. The terminal only sends signed instructions with the permissions you granted.