Available data types
OHLCV candles
TheOHLC endpoint returns candlestick data for a given interval.
Response structure:
[time, open, high, low, close, vwap, volume, count]
Pagination: use the last value from the response as the since parameter in your next call to page forward.
Depth limits:
- Maximum 720 candles per call
- Daily candles (
interval=1440): ~720 days (~2 years) per call - Minute candles (
interval=1): 720 minutes (~12 hours) per call
Trade ticks
TheTrades endpoint returns a time-ordered list of public trades.
Response structure:
[price, volume, time, buy/sell, market/limit, miscellaneous, trade_id]
Pagination: use last as the since value in the next call. The since value is in nanoseconds.
Rate limit note: the Trades endpoint is public and subject to IP-based rate limits. For bulk historical collection, introduce a delay between requests (100–200ms) to avoid throttling.
Order book snapshots
TheDepth endpoint returns the current order book at the time of the request. It is not a historical endpoint — it reflects the live state.
Level3 endpoint:
OrderID values, enabling reconciliation with ExecutionReport data from FIX or the executions WebSocket channel.
Futures historical data
Futures provides dedicated historical endpoints under the Futures REST API:Building a backtesting dataset
A practical approach for collecting a clean historical dataset:1
Collect OHLCV for your timeframe
Start with daily candles to get a broad picture, then drill into minute candles for the periods you need. Use the pagination pattern above.
2
Augment with trade ticks for microstructure
Trade ticks give you the actual execution prices and sizes. Useful for modelling slippage and for tick-by-tick backtesting.
3
Validate against VWAP
Each OHLC candle includes VWAP. Cross-check your collected trade ticks against the VWAP to verify completeness and catch any pagination gaps.
4
Handle gaps
Thin markets or API collection gaps can leave missing candles. Decide upfront how to handle them: forward-fill with the previous close, or exclude those periods from your strategy.
Kraken does not provide a bulk historical data dump or websocket replay service. For very deep history (years of tick data) consider supplementing with third-party data providers.
Rate limits for data collection
Historical data endpoints are public but rate-limited per IP. Recommended safe intervals:
If you need faster collection, distribute requests across multiple IPs or use the FIX market data feed for real-time capture going forward.
Related guides
API comparison
FIX and WebSocket for real-time market data capture
Rate limits
IP-based rate limits for public data endpoints
WebSocket introduction
Stream live market data for forward capture alongside historical backfill