# Binance COIN Futures

Binance COIN Futures historical data for **all its instruments** is available since **2020-06-16**.

{% embed url="<https://api.tardis.dev/v1/exchanges/binance-delivery>" %}
See Binance COIN Futures 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 API key**. See [downloadable CSV files documentation](/downloadable-csv-files/overview.md).

| data type             | symbol         | date       |                                                                                                                        |
| --------------------- | -------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------- |
| incremental\_book\_L2 | BTCUSD\_200925 | 2020-07-01 | [Download sample](https://datasets.tardis.dev/v1/binance-delivery/incremental_book_L2/2020/07/01/BTCUSD_200925.csv.gz) |
| trades                | BTCUSD\_200925 | 2020-07-01 | [Download sample](https://datasets.tardis.dev/v1/binance-delivery/trades/2020/07/01/BTCUSD_200925.csv.gz)              |
| derivative\_ticker    | BTCUSD\_200925 | 2020-07-01 | [Download sample](https://datasets.tardis.dev/v1/binance-delivery/derivative_ticker/2020/07/01/BTCUSD_200925.csv.gz)   |

### API Access and data format

Historical data format is the same as provided by real-time Binance COIN Futures 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 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="binance-delivery",
        from_date="2023-03-01",
        to_date="2023-03-02",
        filters=[Channel(name="depth", symbols=["btcusd_perp"])],
        api_key="YOUR_API_KEY",
    ):
        # messages as provided by Binance COIN Futures 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: 'binance-delivery',
  from: '2023-03-01',
  to: '2023-03-02',
  filters: [{ channel: 'depth', symbols: ['btcusd_perp'] }],
  apiKey: 'YOUR_API_KEY'
});

// messages as provided by Binance COIN Futures 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/binance-delivery?from=2023-03-01&filters=[{"channel":"depth","symbols":["btcusd_perp"]}]&offset=0'
```

{% embed url="<https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2023-03-01&filters=[{%22channel%22:%22depth%22,%22symbols%22:[%22btcusd_perp%22]}]&offset=0>" %}
Example API response for Binance COIN Futures 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":"binance-delivery","filters":[{"channel":"depth","symbols":["btcusd_perp"]}],"from":"2023-03-01","to":"2023-03-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://binance-docs.github.io/apidocs/delivery/en/#websocket-market-streams>" %}
See Binance COIN Futures 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 %}

* [trade](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22trade%22}]) Public COIN futures trade executions stream
* [depth](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22depth%22,%22symbols%22:\[%22btcusd_perp%22]}]) Incremental COIN futures order book updates stream. Subscribed as `depth@0ms` with real-time dynamically adjusted update speed.
* [depthSnapshot](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22depthSnapshot%22,%22symbols%22:\[%22btcusd_perp%22]}]) — generated channel Binance COIN Futures real-time WebSocket API **does not provide initial order book snapshots**. To overcome this issue we fetch initial order book snapshots from REST API and store them together with the rest of the WebSocket messages — top 1000 levels. Such snapshot messages are marked with `"stream":"<symbol>@depthSnapshot"` and `"generated":true` fields.

  During data collection integrity of order book incremental updates is being validated using [sequence numbers](https://binance-docs.github.io/apidocs/delivery/en/#diff-book-depth-streams) provided by real-time feed (`U` and `u` fields) — in case of detecting missed message WebSocket connection is being restarted. We also validate if initial book snapshot fetched from REST API overlaps with received `depth` messages.
* [bookTicker](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22bookTicker%22}]) Best bid and best ask updates stream
* [forceOrder](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22forceOrder%22}]) — available since **2020-07-08** Liquidation order stream publishing only the latest liquidation per symbol in each 1000ms window
* [markPrice](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22markPrice%22}]) Mark price and funding metrics stream subscribed as `@markPrice@1s`
* [indexPrice](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22indexPrice%22}]) Index price updates stream subscribed as `@indexPrice@1s`
* [openInterest](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22openInterest%22,%22symbols%22:\[%22btcusd_perp%22]}]) — generated channel

  Snapshots are fetched from the REST [open interest endpoint](https://binance-docs.github.io/apidocs/delivery/en/#open-interest) about every 6 seconds per instrument. Messages are marked with `"stream":"<symbol>@openInterest"` and `"generated":true` fields with REST response format.
* [fundingInfo](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2026-03-17\&filters=\[{%22channel%22:%22fundingInfo%22}]) — generated channel, available since **2026-03-17**

  Snapshots are fetched from the REST [funding info endpoint](https://developers.binance.com/docs/derivatives/coin-margined-futures/market-data/rest-api/Get-Funding-Info) every minute. Binance returns only symbols with adjusted funding cap, floor, or interval. Messages are marked with `"stream":"<symbol>@fundingInfo"` and `"generated":true` fields with REST response format.
* [aggTrade](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22aggTrade%22}]) Aggregated COIN futures trade executions stream
* [ticker](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-01-01\&filters=\[{%22channel%22:%22ticker%22}]) 24h COIN futures ticker updates stream
* [topLongShortAccountRatio](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-02-01\&filters=\[{%22channel%22:%22topLongShortAccountRatio%22,%22symbols%22:\[]}]\&offset=4) — generated channel, available since **2020-10-28**

  Top trader long/short ratio (accounts), sourced by querying REST endpoint every minute
* [topLongShortPositionRatio](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-02-01\&filters=\[{%22channel%22:%22topLongShortPositionRatio%22,%22symbols%22:\[]}]\&offset=4) — generated channel, available since **2020-10-28**

  Top trader long/short ratio (positions), sourced by querying REST endpoint every minute
* [globalLongShortAccountRatio](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-02-01\&filters=\[{%22channel%22:%22globalLongShortAccountRatio%22,%22symbols%22:\[]}]\&offset=4) — generated channel, available since **2020-10-28**

  Global long/short ratio, sourced by querying REST endpoint every minute
* [takerBuySellVol](https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2024-02-01\&filters=\[{%22channel%22:%22takerBuySellVol%22,%22symbols%22:\[]}]\&offset=4) — generated channel, available since **2021-12-01**

  Taker buy/sell volume ratio, sourced by querying REST endpoint every minute
* `!contractInfo` — available since **2023-04-01** Contract metadata updates stream pushed when listing, settlement, or bracket information changes

### Market data collection details

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

Real-time market data is captured via **multiple WebSocket connections** to `wss://dstream.binance.com/stream`.

{% hint style="info" %}
Binance servers are located in AWS ap-northeast-1 region (Tokyo, Japan).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tardis.dev/historical-data-details/binance-delivery.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
