> 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/gemini.md).

# Gemini

Gemini historical market data details - instruments, data coverage and data collection specifics

Gemini exchange historical data for **all its supported instruments** is available since **2019-08-30**.

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

### 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 | BTCUSD | 2020-01-01 | [Download sample](https://datasets.tardis.dev/v1/gemini/incremental_book_L2/2020/01/01/BTCUSD.csv.gz) |
| trades                | BTCUSD | 2020-01-01 | [Download sample](https://datasets.tardis.dev/v1/gemini/trades/2020/01/01/BTCUSD.csv.gz)              |
| quotes                | BTCUSD | 2020-01-01 | [Download sample](https://datasets.tardis.dev/v1/gemini/quotes/2020/01/01/BTCUSD.csv.gz)              |
| book\_ticker          | BTCUSD | 2026-08-01 | [Download sample](https://datasets.tardis.dev/v1/gemini/book_ticker/2026/08/01/BTCUSD.csv.gz)         |

### API Access and data format

Historical data uses the exchange-native Gemini WebSocket format with the addition of local timestamps. Data recorded before **2026-07-24** UTC uses Gemini **Market Data Version 2**; data recorded from **2026-07-24** UTC uses Gemini WebSocket API **v3**.

Gemini v3 raw payloads use lowercase symbols, for example `btcusd`. For backward compatibility with Gemini v2, whose raw payloads used uppercase symbols, Tardis symbol IDs and normalized messages remain uppercase. Gemini symbol filters are case-insensitive, so existing filters such as `BTCUSD` continue to match v3 messages for `btcusd`.

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="gemini",
        from_date="2026-08-01",
        to_date="2026-08-02",
        filters=[Channel(name="depth", symbols=["BTCUSD"])],
        api_key="YOUR_API_KEY",
    ):
        # messages as provided by Gemini 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: 'gemini',
  from: '2026-08-01',
  to: '2026-08-02',
  filters: [{ channel: 'depth', symbols: ['BTCUSD'] }],
  apiKey: 'YOUR_API_KEY'
});

// messages as provided by Gemini 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/gemini?from=2026-08-01&filters=[{"channel":"depth","symbols":["BTCUSD"]}]&offset=0'
```

{% embed url="<https://api.tardis.dev/v1/data-feeds/gemini?from=2026-08-01&filters=[{%22channel%22:%22depth%22,%22symbols%22:[%22BTCUSD%22]}]&offset=0>" %}
Example API response for Gemini 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":"gemini","filters":[{"channel":"depth","symbols":["BTCUSD"]}],"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://developer.gemini.com/websocket/streams>" %}
See Gemini WebSocket API docs for current channel formats
{% 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 v3, since 2026-07-24):**

* [trade](https://api.tardis.dev/v1/data-feeds/gemini?from=2026-08-01\&filters=\[{%22channel%22:%22trade%22}]) Public trade executions stream
* [depth](https://api.tardis.dev/v1/data-feeds/gemini?from=2026-08-01\&filters=\[{%22channel%22:%22depth%22}]) Incremental level 2 order book updates captured from Gemini's `{symbol}@depth@100ms` stream. Collection uses `snapshot=-1`, so the first `depthUpdate` for each symbol and connection is a full order book snapshot; subsequent messages are incremental updates.
* [bookTicker](https://api.tardis.dev/v1/data-feeds/gemini?from=2026-08-01\&filters=\[{%22channel%22:%22bookTicker%22}]) Best bid and ask price and quantity updates

**Legacy channels (API v2, until 2026-07-24):**

Legacy v2 message formats are documented in the [archived Gemini Market Data Version 2 documentation](https://web.archive.org/web/20250130160317/https://docs.gemini.com/websocket-api/#market-data-version-2).

* [trade](https://api.tardis.dev/v1/data-feeds/gemini?from=2024-01-01\&filters=\[{%22channel%22:%22trade%22}]) Public trade executions stream
* [l2\_updates](https://api.tardis.dev/v1/data-feeds/gemini?from=2024-01-01\&filters=\[{%22channel%22:%22l2_updates%22}]) Level 2 order book deltas stream
* [auction\_open](https://api.tardis.dev/v1/data-feeds/gemini?from=2024-01-01\&filters=\[{%22channel%22:%22auction_open%22}]) Auction open events stream
* [auction\_indicative](https://api.tardis.dev/v1/data-feeds/gemini?from=2024-01-01\&filters=\[{%22channel%22:%22auction_indicative%22}]) Auction indicative price and quantity updates
* [auction\_result](https://api.tardis.dev/v1/data-feeds/gemini?from=2024-01-01\&filters=\[{%22channel%22:%22auction_result%22}]) Auction result events stream

### Market data collection details

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

Real-time market data is captured via **multiple WebSocket connections** to Gemini WebSocket API v3 at `wss://ws.gemini.com?snapshot=-1`. Before **2026-07-24**, data was captured from API v2 at `wss://api.gemini.com/v2/marketdata`.

{% hint style="info" %}
Gemini servers are located in AWS us-east-1 region (N. Virginia, 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/gemini.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.