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

# Coinbase International

Coinbase International historical market data details - instruments, data coverage and data collection specifics

{% hint style="info" %}
Coinbase International market data is subject to Coinbase market data license restrictions.

See the applicable [Coinbase market data license restrictions](https://docs.tardis.dev/historical-data-details/pages/-LkYDB4Q2h9uctu9Kq7Y#id-23.-coinbase-market-data-license-restrictions).
{% endhint %}

Coinbase International historical data for **all its instruments** is available since **2024-10-31** until **2026-10-01 00:00 UTC** (exclusive).

Collection ended when [Coinbase International Exchange migrated its trading to Deribit](https://status.international.coinbase.com/incidents/b2szg88w5s6d) on **2026-10-01**. Coinbase International Exchange remains available in read-only mode, and its former perpetual contracts trade on [Deribit](/historical-data-details/deribit.md).

{% embed url="<https://api.tardis.dev/v1/exchanges/coinbase-international>" %}
See Coinbase International 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 | BTC-PERP | 2025-01-01 | [Download sample](https://datasets.tardis.dev/v1/coinbase-international/incremental_book_L2/2025/01/01/BTC-PERP.csv.gz) |
| trades                | BTC-PERP | 2025-01-01 | [Download sample](https://datasets.tardis.dev/v1/coinbase-international/trades/2025/01/01/BTC-PERP.csv.gz)              |
| derivative\_ticker    | BTC-PERP | 2025-01-01 | [Download sample](https://datasets.tardis.dev/v1/coinbase-international/derivative_ticker/2025/01/01/BTC-PERP.csv.gz)   |

### API Access and data format

Historical data format is the same as provided by real-time Coinbase International WebSocket API with addition of local timestamps. 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="coinbase-international",
        from_date="2024-11-01",
        to_date="2024-11-02",
        filters=[Channel(name="LEVEL2", symbols=["BTC-PERP"])],
        api_key="YOUR_API_KEY",
    ):
        # messages as provided by Coinbase International 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: 'coinbase-international',
  from: '2024-11-01',
  to: '2024-11-02',
  filters: [{ channel: 'LEVEL2', symbols: ['BTC-PERP'] }],
  apiKey: 'YOUR_API_KEY'
});

// messages as provided by Coinbase International 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/coinbase-international?from=2024-11-01&filters=[{"channel":"LEVEL2","symbols":["BTC-PERP"]}]&offset=0'
```

{% embed url="<https://api.tardis.dev/v1/data-feeds/coinbase-international?from=2024-11-01&filters=[{%22channel%22:%22LEVEL2%22,%22symbols%22:[%22BTC-PERP%22]}]&offset=0>" %}
Example API response for Coinbase International 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":"coinbase-international","filters":[{"channel":"LEVEL2","symbols":["BTC-PERP"]}],"from":"2024-11-01","to":"2024-11-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.cdp.coinbase.com/international-exchange/websocket-feed/channels>" %}
See Coinbase International 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 %}

* [MATCH](https://api.tardis.dev/v1/data-feeds/coinbase-international?from=2025-01-01\&filters=\[{%22channel%22:%22MATCH%22}]) Trade match events stream
* [LEVEL2](https://api.tardis.dev/v1/data-feeds/coinbase-international?from=2025-01-01\&filters=\[{%22channel%22:%22LEVEL2%22,%22symbols%22:\[%22BTC-PERP%22]}]) Order book snapshots and deltas
* [LEVEL1](https://api.tardis.dev/v1/data-feeds/coinbase-international?from=2025-01-01\&filters=\[{%22channel%22:%22LEVEL1%22,%22symbols%22:\[%22BTC-PERP%22]}]) Top of book bid and ask updates
* [FUNDING](https://api.tardis.dev/v1/data-feeds/coinbase-international?from=2025-01-01\&filters=\[{%22channel%22:%22FUNDING%22}]) Funding rate and next funding time updates
* [RISK](https://api.tardis.dev/v1/data-feeds/coinbase-international?from=2025-01-01\&filters=\[{%22channel%22:%22RISK%22}]) Risk parameter updates
* [INSTRUMENTS](https://api.tardis.dev/v1/data-feeds/coinbase-international?from=2025-01-01\&filters=\[{%22channel%22:%22INSTRUMENTS%22}]) Instrument metadata and trading state updates
* [CANDLES\_ONE\_MINUTE](https://api.tardis.dev/v1/data-feeds/coinbase-international?from=2025-01-01\&filters=\[{%22channel%22:%22CANDLES_ONE_MINUTE%22}]) One minute candle updates

### Market data collection details

[Market data collection infrastructure](/faq/general.md#what-is-your-infrastructure-setup) for Coinbase International was located in GCP asia-northeast1 region (Tokyo, Japan).

Real-time market data was captured via **multiple WebSocket connections** to `wss://ws-md.international.coinbase.com`.

{% hint style="info" %}
Coinbase International servers were located in AWS ap-northeast-1 region (Tokyo, Japan).
{% 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/coinbase-international.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.