Skip to main content
The Kraken Unified FIX API is a FIX 4.4 implementation that covers both Spot and Derivatives markets through a single set of credentials. It is the lowest-latency order-entry path on the platform, with deterministic sequencing, cancel-on-disconnect, and session-based message replay. For protocol architecture, supported messages, ClOrdID rules, STP, and performance details, see the FIX overview guide.

​
Connection

EnvironmentHostname
Productioncolo-london.vip-fix.kraken.com
UATcolo-london.vip-fix.uat.kraken.com
ServicePort
Spot Trading4001
Spot Market Data (L2)4000
Spot Market Data (L3)4005
Derivatives Trading4003
Derivatives Market Data (L2)4002
Derivatives Market Data (L3)4004
All connections use TCP with TLS 1.3. DNS records carry a 5-minute TTL — always resolve at connection time, never bind to static IPs.

​
Authentication

Authentication uses a Spot FIX API Key. The same key authorises both Spot and Derivatives sessions on the appropriate ports — no separate Derivatives FIX credentials are required. See FIX authentication for the logon message structure, IP allow-listing, and CompID provisioning.

​
Hours of operation

FIX sessions operate 24/7 with a logical session rollover every day at 22:00 UTC. The rollover lasts approximately 30 seconds. Both Trading and Market Data sequence numbers reset to 0 after rollover.

​
Cancel scope

Single-order cancels on FIX (OrderCancelRequest) only affect orders placed on the same FIX session. To cancel orders placed on another session — whether FIX, WebSocket, or REST — use OrderMassCancelRequest (Tag 35=q) or fall back to REST/WebSocket.

​
Quick start

Logon

Session establishment and parameters.

NewOrderSingle (D)

Place an order on Spot or Derivatives.

ExecutionReport (8)

Order acknowledgements, fills, cancels, and rejects.

OrderMassCancelRequest (q)

Cancel all orders on the account, regardless of session.
The full message catalog — OrderCancelRequest, OrderCancelReplaceRequest, MarketDataRequest, OrderStatusRequest, ResendRequest, SequenceReset, headers/trailers, and reject types — is available in the Unified FIX dropdown in the left navigation.
Access to direct colocation requires VIP status, an executed NDA, and an Equinix London presence. Contact your Account Manager to begin onboarding.

FIX overview

Session architecture, supported messages, performance, ports.

FIX authentication

Logon message and CompID setup.

Choose your protocol

REST vs WebSocket vs FIX — sequencing, cancel scope, latency.

Colocation and connectivity

Connectivity tiers, latency expectations, LOA process.