35=A) must be the first message sent after establishing the TCP connection. It authenticates the session and sets session-level parameters.
If logon succeeds, Kraken responds with a Logon message. If it fails, Kraken sends a Logout with a reason, or silently closes the connection.
Session Types
Kraken FIX offers two session types that use different TargetCompIDs and have different authentication requirements:Spot and Derivatives use separate SenderCompIDs. Your Derivatives SenderCompID will have a
DRV suffix. Both are provided by Kraken during onboarding.Fields
required
35=
Ainteger
required
Always set to
0 (None).integer
required
Heartbeat interval in seconds. Recommended value:
60.string
Your FIX API Key. Create it in Kraken Pro settings with FIX as the key type.Condition: Trading session only
string
HMAC-SHA512 signature. See Password Generation below.Condition: Trading session only
string
Current timestamp in milliseconds since Unix epoch, as a string.Condition: Trading session only
integer
Associates this connection with another connection (e.g. linking a trading session to a market data session).
boolean
If
Y, both sides reset their sequence numbers to 1. Use on initial connect or after a session reset. Default: N.integer
Controls what happens to open orders if the session disconnects.Possible values:
0— Cancel all open orders placed during this session (default)1— Leave open orders in place after disconnect
boolean
Resets your ClOrdID sequence on re-logon. Use in emergencies only. Default:
N.boolean
Applies to xStocks trading only.
N— Orders and execution reports use SPV token quantities (default)Y— Orders and execution reports use underlying equity quantities (Kraken applies the multiplier automatically)
required
Password Generation
The password is computed as:\x01):
Nonce (tag 5025) and the value used in MessageInput must be identical. Generate nonce once and use it in both places.