Spot. WebSocket snapshot, then deltas.
Messages / s and KB / s are what our handler receives from the exchange (KB after decompression, REST snapshots included); level changes / s are counted after normalization, for the markets we publish.
Open live books Replaywss://ws.kraken.com/v2BTC/USDT{"method":"subscribe","params":{"channel":"book","symbol":["BTC/USDT","ETH/USDT",...],"depth":100}}
Our execution provider for US Futures has scheduled maintenance starting at 00:30 UTC on 21 November, planned for up to 1.5 hours. This affects US Futures only (CME Group 24/7 futures products and Bitnomial perpetual futures). During the window, clients will not be able to place, modify, cancel, or close orders or positions, including via API. Market data may also be affected. We recommend closing any positions and canceling any working orders you do not wish to carry into the maintenance window. Linear multi-collateral derivatives for non-US clients and all other products are not affected.
Our handler: Affects: Market Data, Bitnomial Exchange (BTNL), Order Placement
Use POST /transfer with toAccount=spot instead of POST /withdrawal. Transfers made with POST /transfer appear in the account log rather than in GET /transfers. These are account and funds endpoints only.
Our handler: Affects Derivatives account endpoints /withdrawal and /transfers, which our public Spot market data handler does not use.
The Unified WebSocket streams Spot and Derivatives on one connection and selects Derivatives with asset_class=derivatives. Kraken's Rust SDK now supports Futures on it. Only clients using the Derivatives WS v1 need to migrate.
Our handler: We consume only Spot via wss://ws.kraken.com/v2, not the Derivatives WebSocket v1 host.
The scheduled maintenance has been completed.
Our handler: Affects: WebSocket, Unified WebSocket
Spot transfers need an API key with withdrawal permission and cost 100 rate-limit units. Futures-to-Futures transfers cost 10 units and now return specific refusal reasons instead of always insufficientFunds. This is an account and funds change with no effect on public market data.
Our handler: Concerns Derivatives account transfer endpoints (/transfer, /transfer/assets), not the Spot WS v2 book or trade channels.
The new error is makerProtectionOrderLimitExceeded (REST v3), MAKER_PROTECTION_ORDER_LIMIT_EXCEEDED (REST v4 and FIX). It was previously reported as tooManyOrders. This is a trading-only change.
Our handler: Applies to Derivatives order-entry errors and the cancelallorders endpoint, not public market data.
We will be undergoing scheduled maintenance during this time.
Our handler: Affects: User Interface, Single Sign-On, REST API, Websocket API, Cross-Exchange Transfers, FIX API
Kraken Prime will be undergoing maintenance as we upgrade our systems on Thursday, Nov 19 at 21:00 UTC. Existing connections will be disconnected and reconnection is possible after the 15 minute maintenance window. We kindly advise our clients to plan ahead accordingly and make necessary account adjustments prior to the start of the maintenance.
Our handler: Affects: FIX, REST, WebSocket
We're pleased to announce that the Unified WebSocket API is now available for Derivatives. It gives clients a single WebSocket interface for both spot and derivatives. Spot is expected early next year. Along with market data and accounting, trading is now also available for derivatives via WebSocket. The public endpoint is uws.kraken.com/v2/public, while the private one is uws.kraken.com/v2/private. SDKs to integrate with Unified WebSocket are now available. The Derivatives WebSocket APIs are now deprecated and will be decommissioned on 1st March 2027. Documentation: https://docs.kraken.com/exchange/api-reference/unified-websocket SDKs: https://docs.kraken.com/home/sdks/index If you have questions or run into issues, please contact Kraken Support.
Our handler: Affects: Websocket API, Unified WebSocket
Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed
Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.