TL;DR:
- Kraken’s API offers real-time and historic market information feeds to totally different technique varieties: L2 order e book depth for execution algorithms, OHLCV and commerce historical past for backtesting, funding price information for carry methods, and ticker feeds for momentum indicators.
- Systematic merchants sometimes use 2–3 feeds primarily based on technique kind, over-subscribing provides overhead with out bettering sign high quality.
Realizing which API endpoints exist doesn’t inform you which feeds to really use. Execution algorithms generally use L2 e book depth 10 moderately than 1,000. Momentum methods sometimes don’t want an order e book in any respect. And should you’re backtesting on 6 months of information, you’re lacking how your technique performs throughout market cycles.
What market information feeds does Kraken’s API supply?
- Actual-time feeds: Ticker (value/quantity), order e book (L2 depth, L3 particular person orders), trades (executed transactions), OHLCV (streaming candlesticks)
- Historic information: OHLCV, historic funding charges, commerce historical past
- Futures-specific: Mark value, funding charges, open curiosity
- Entry strategies: WebSocket v2 for real-time, REST for historic, FIX for institutional
Do you want L2 or L3 order e book information in your crypto buying and selling technique?
Ticker information offers finest bid, finest ask, and final value. However should you’re executing measurement, ticker alone doesn’t inform you how a lot liquidity sits behind these costs.
L2 (aggregated orders)
Order e book (L2) reveals aggregated depth throughout a number of value ranges. This issues whenever you’re sizing orders to keep away from slippage. Should you’re promoting 5 BTC and one of the best bid solely has 0.08 BTC of depth, you’ll transfer via a number of ranges. L2 reveals you this earlier than you ship the order.
L3 (particular person orders)
L3 offers a full order-by-order view of all resting orders within the e book, together with order IDs and timestamps. This allows queue precedence evaluation; you possibly can decide the place any order, together with your personal, sits within the queue at every value stage, in addition to fill chance estimation and market microstructure evaluation. L3 is primarily used for sub-second execution or queue place evaluation.
From a efficiency standpoint, the latency distinction between L3 and L2 feeds is negligible in comparison with transport time. The principle value is payload measurement: L3 describes each particular person order within the e book moderately than cumulative amount at every value stage, which suggests extra information to encode, transmit, and decode. Should you can’t articulate why you want particular person order visibility, L2 is ample for many systematic methods.
Depth choices
The WebSocket e book channel helps 5 depth ranges — 10, 25, 100, 500, and 1,000. Execution algorithms generally use depth 10, which covers the actionable vary with minimal payload overhead. Depths 500 and 1,000 are used for market affect modeling or analyzing deep liquidity and are extra compute-intensive to take care of.
How do you entry Kraken’s historic market information for backtesting?
OHLCV (candlestick information) is usually used for backtesting. Shifting averages, RSI, breakout indicators, all of them use OHLCV as enter.
However OHLCV alone doesn’t inform you in case your execution assumptions are lifelike. In case your backtest assumes you possibly can fill 10 BTC at bid with out slippage, it is best to validate that towards commerce historical past. Pull the commerce feed to verify that quantity really traded at these ranges throughout your backtest interval.
WebSocket vs REST for OHLCV: Use WebSocket should you want the present candle up to date in real-time as trades occur, moderately than polling for a accomplished candle.
How do you employ Kraken’s funding price information for carry methods?
Funding price carry methods harvest the periodic funds between longs and shorts on perpetual futures. You want present charges for reside monitoring (futures ticker offers this) and historic charges for backtesting.
Mark value vs. index value: The futures ticker consists of each, together with the final traded value, three distinct values. Mark value determines liquidation danger and unrealized P&L. The index value is the real-time spot reference value utilized in funding price calculations. Throughout risky intervals, mark value and index value can diverge; when that unfold widens, it indicators foundation danger or liquidation strain, one thing carry merchants want to observe carefully. The final traded value is a separate determine reflecting the latest fill and isn’t the related comparability for assessing liquidation danger.
What are the most typical errors when utilizing crypto market information feeds?
- Utilizing WebSocket for all the pieces: Should you’re backtesting or operating sluggish methods, REST polling is easier.
- Assuming L3 is critical.: Should you can’t clarify why you want particular person order visibility and queue place information throughout the total e book, you most likely don’t want L3. Order e book L2 (aggregated depth) is ample for many systematic methods.
- Ignoring historic depth: A backtest on 6 months of information doesn’t present you the way your technique performs throughout market cycles.
How do you get began with market information feeds on Kraken?
New to Kraken’s API? Begin with ticker and OHLCV through REST. These are public (no authentication), easy to combine, and canopy most of preliminary technique growth. Add order e book and commerce feeds whenever you transfer to reside execution.
For knowledgeable merchants:
- Establish your technique kind: Execution algo, backtest, momentum, and so on
- Choose 2-3 feeds: Don’t over-subscribe, begin with what instantly feeds your indicators or execution logic
- Create API keys when prepared
- Full API documentation: docs.kraken.com/api
Create your API keys now, or for institutional scale or FIX entry, get in contact:
FAQ
What market information does Kraken’s API present at no cost?
Kraken’s real-time market information feeds (ticker, order e book (L2), trades, and OHLCV) don’t require authentication. L3 particular person order information requires authentication.
What’s the distinction between L2 and L3 order e book information on Kraken?
L2 reveals aggregated depth throughout value ranges, which is ample for many systematic methods. L3 reveals all particular person resting orders within the e book with order IDs and timestamps, enabling queue precedence evaluation, fill chance estimation, and market microstructure evaluation. L3 requires authentication. Should you can’t clarify why you want full particular person order visibility, you most likely don’t want it.
Ought to I take advantage of WebSocket or REST for crypto market information?
Use WebSocket should you want the present candle up to date in real-time as trades occur, moderately than polling for a accomplished candle.
What information feeds do I want for a crypto execution algorithm?
Execution algorithms generally use L2 order e book depth. The WebSocket e book channel helps depths of 10, 25, 100, 500, and 1,000. Depth 10 is the usual start line and covers the actionable vary. Depths of 500 and 1,000 are used for market affect modeling and analyzing deep liquidity. Ticker information alone is inadequate when executing measurement as a result of it doesn’t present liquidity behind finest bid/ask.
