> For the complete documentation index, see [llms.txt](https://docs.tardis.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tardis.dev/historical-data-details/kraken.md).

# Kraken

Kraken historical market data details - currency pairs, data coverage and data collection specifics

Kraken historical data for **all its currency pairs** is available since **2019-06-04**.

{% embed url="<https://api.tardis.dev/v1/exchanges/kraken>" %}
See Kraken historical data coverage: available symbols, channels, date ranges and incidents
{% endembed %}

### Symbol changes

Kraken WebSocket v2 uses `BTC` and `DOGE` in exchange-native symbol IDs. WebSocket v1 used `XBT` and `XDG`. Use v1 symbols before **2026-07-10** and v2 symbols from that date onward. This applies to both base and quote currencies, for example:

* `XBT/USD` → `BTC/USD`
* `XDG/USD` → `DOGE/USD`
* `ETH/XBT` → `ETH/BTC`

To resolve symbol IDs programmatically, query the [Instruments Metadata API](/api/instruments-metadata-api.md) using normalized `baseCurrency` and `quoteCurrency` values:

```json
{
  "baseCurrency": "BTC",
  "quoteCurrency": "USD",
  "type": "spot"
}
```

The response includes both exchange-native symbol IDs:

| id        | active  | availableSince             | availableTo                |
| --------- | ------- | -------------------------- | -------------------------- |
| `XBT/USD` | `false` | `2019-06-04T00:00:00.000Z` | `2026-07-10T00:00:00.000Z` |
| `BTC/USD` | `true`  | `2026-07-10T00:00:00.000Z` |                            |

### Downloadable **CSV** files

Historical CSV datasets for the first day of each month are **available to download without a Data API key**. See [downloadable CSV files documentation](/downloadable-csv-files/overview.md).

| data type             | symbol  | date       |                                                                                                        |
| --------------------- | ------- | ---------- | ------------------------------------------------------------------------------------------------------ |
| incremental\_book\_L2 | XBT-USD | 2019-07-01 | [Download sample](https://datasets.tardis.dev/v1/kraken/incremental_book_L2/2019/07/01/XBT-USD.csv.gz) |
| trades                | XBT-USD | 2019-07-01 | [Download sample](https://datasets.tardis.dev/v1/kraken/trades/2019/07/01/XBT-USD.csv.gz)              |
| quotes                | XBT-USD | 2019-07-01 | [Download sample](https://datasets.tardis.dev/v1/kraken/quotes/2019/07/01/XBT-USD.csv.gz)              |

### API Access and data format

Historical data format is the same as provided by real-time Kraken WebSocket **v2** API from **2026-07-10** onward, with addition of local timestamps. Data before **2026-07-10** uses Kraken WebSocket **v1** format. If you'd like to work with **normalized data format** instead (same format for each exchange) see [downloadable CSV files](/downloadable-csv-files/overview.md) or official [client libs](/api/quickstart.md) that can perform data normalization client-side.

{% tabs %}
{% tab title="Python" %}

```python
# pip install tardis-dev
import asyncio
from tardis_dev import Channel, replay

async def main():
    async for local_timestamp, message in replay(
        exchange="kraken",
        from_date="2026-08-01",
        to_date="2026-08-02",
        filters=[Channel(name="book", symbols=["BTC/USD"])],
        api_key="YOUR_API_KEY",
    ):
        # messages as provided by Kraken real-time stream
        print(message)

asyncio.run(main())
```

See [Python client docs](/python-client/quickstart.md).
{% endtab %}

{% tab title="Node.js" %}

```javascript
// npm install tardis-dev
import { replay } from 'tardis-dev';

const messages = replay({
  exchange: 'kraken',
  from: '2026-08-01',
  to: '2026-08-02',
  filters: [{ channel: 'book', symbols: ['BTC/USD'] }],
  apiKey: 'YOUR_API_KEY'
});

// messages as provided by Kraken real-time stream
for await (const { localTimestamp, message } of messages) {
  console.log(localTimestamp, message);
}
```

See [Node.js client docs](/node-client/quickstart.md).
{% endtab %}

{% tab title="cURL & HTTP API" %}

```bash
curl --compressed -g 'https://api.tardis.dev/v1/data-feeds/kraken?from=2026-08-01&filters=[{"channel":"book","symbols":["BTC/USD"]}]&offset=0'
```

{% embed url="<https://api.tardis.dev/v1/data-feeds/kraken?from=2026-08-01&filters=[{%22channel%22:%22book%22,%22symbols%22:[%22BTC/USD%22]}]&offset=0>" %}
Example API response for Kraken historical market data request
{% endembed %}

See [HTTP API docs](/api/http-api-reference.md).
{% endtab %}

{% tab title="cURL & tardis-machine" %}

```bash
curl -g 'localhost:8000/replay?options={"exchange":"kraken","filters":[{"channel":"book","symbols":["BTC/USD"]}],"from":"2026-08-01","to":"2026-08-02"}'
```

[Tardis-machine](/tardis-machine/quickstart.md) is a locally runnable server that exposes API allowing efficiently requesting historical market data for whole time periods in contrast to [HTTP API](/api/http-api-reference.md) that provides data only in minute by minute slices.

See [tardis-machine](/tardis-machine/quickstart.md) docs.
{% endtab %}
{% endtabs %}

### Captured real-time channels

{% embed url="<https://docs.kraken.com/exchange/api-reference/spot-websocket>" %}
See Kraken WebSocket API docs providing documentation for each captured channel's format
{% endembed %}

{% hint style="info" %}
Click any channel below to see [HTTP API](/api/http-api-reference.md#data-feeds-exchange) response with historical data recorded for it.
{% endhint %}

**Current channels (API v2, since 2026-07-10):**

* [trade](https://api.tardis.dev/v1/data-feeds/kraken?from=2026-08-01\&filters=\[{%22channel%22:%22trade%22}]) Public trade executions stream
* [book](https://api.tardis.dev/v1/data-feeds/kraken?from=2026-08-01\&filters=\[{%22channel%22:%22book%22,%22symbols%22:\[%22BTC/USD%22]}]) Level 2 order book snapshots and updates with `depth=1000`
* [ticker](https://api.tardis.dev/v1/data-feeds/kraken?from=2026-08-01\&filters=\[{%22channel%22:%22ticker%22}]) Level 1 market data and 24h statistics, published when the best bid or offer changes (`event_trigger=bbo`)
* [instrument](https://api.tardis.dev/v1/data-feeds/kraken?from=2026-08-01\&filters=\[{%22channel%22:%22instrument%22}]) Reference data snapshots and updates for all active assets and tradeable pairs, including tokenized assets

**Legacy channels (API v1, until 2026-07-10):**

* [trade](https://api.tardis.dev/v1/data-feeds/kraken?from=2024-01-01\&filters=\[{%22channel%22:%22trade%22}]) Public trade executions stream
* [book](https://api.tardis.dev/v1/data-feeds/kraken?from=2024-01-01\&filters=\[{%22channel%22:%22book%22,%22symbols%22:\[%22XBT/USD%22]}]) Order book snapshots and deltas recorded with depth=1000
* [spread](https://api.tardis.dev/v1/data-feeds/kraken?from=2024-01-01\&filters=\[{%22channel%22:%22spread%22,%22symbols%22:\[%22XBT/USD%22]}]) Best bid and ask spread updates stream
* [ticker](https://api.tardis.dev/v1/data-feeds/kraken?from=2024-01-01\&filters=\[{%22channel%22:%22ticker%22}]) Ticker updates with best bid and ask plus 24h stats

### Market data collection details

[Market data collection infrastructure](/faq/general.md#what-is-your-infrastructure-setup) for Kraken is located in GCP europe-west2 region (London, UK).

Real-time market data is captured via **multiple WebSocket connections** to `wss://ws.kraken.com/v2`. Before **2026-07-10**, data was captured from Kraken WebSocket v1 at `wss://ws.kraken.com`.

{% hint style="info" %}
Kraken servers are located in Equinix data center (London, UK) since **2025-11-01**. Before that they were located in AWS eu-west-1 region (Dublin, Ireland) from **2024-01-20**, and initially in AWS us-west-2 region (Oregon, USA).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tardis.dev/historical-data-details/kraken.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.