Binance Delivery Futures

Binance Delivery Futures historical data for all it's instruments is available since 2020-06-16.

​

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.

​

API Access and data format

Historical data format is the same as provided by real-time Binance Delivery 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 or official client libs that perform data normalization client-side.

# pip install tardis-client
import asyncio
from tardis_client import TardisClient, Channel
tardis_client = TardisClient(api_key="YOUR_API_KEY")
​
async def replay():
  # replay method returns Async Generator
  messages = tardis_client.replay(
    exchange="binance-delivery",
    from_date="2020-07-01",
    to_date="2020-07-02",
    filters=[Channel(name="depth", symbols=["btcusd_200925"])]
  )
​
  # messages as provided by Binance Delivery Futures real-time stream
  async for local_timestamp, message in messages:
    print(message)
​
​
asyncio.run(replay())

// npm install tardis-dev
const { replay } = require('tardis-dev');
​
async function run() {
  try {
    const messages = replay({
      exchange: 'binance-delivery',
      from: '2020-07-01',
      to: '2020-07-02',
      filters: [{ channel: 'depth', symbols: ['btcusd_200925'] }],
      apiKey: 'YOUR_API_KEY'
    });
​
    // messages as provided by Binance Delivery Futures real-time stream
    for await (const { localTimestamp, message } of messages) {
      console.log(localTimestamp, message);
    }
  } catch (e) {
    console.error(e);
  }
}
​
run();

curl -g 'https://api.tardis.dev/v1/data-feeds/binance-delivery?from=2020-07-01&filters=[{"channel":"depth","symbols":["btcusd_200925"]}]&offset=0'

curl -g 'localhost:8000/replay?options={"exchange":"binance-delivery","filters":[{"channel":"depth","symbols":["btcusd_200925"]}],"from":"2020-07-01","to":"2020-07-02"}'

​

Captured real-time channels

​

• ​trade​

• ​aggTrade​

• ​ticker​

• ​bookTicker​

• ​forceOrder​

• ​markPrice @1s

• ​indexPrice @1s

• ​depth @0ms

• ​depthSnapshot - generated channel with full order book snapshots Binance Delivery 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 provided by real-time feed (pu 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.

• ​openInterest - generated channel

  Since Binance Delivery Futures does not offer currently real-time WebSocket open interest channel, we simulate it by fetching that info from REST API (https://binance-docs.github.io/apidocs/delivery/en/#open-interest) every 30 seconds for each instrument. Such messages are marked with "stream":"<symbol>@openInterest" and "generated":true fields and data field has the same format as REST API response.

  ​

• ​recentTrades - generated channel After establishing successful real-time WebSocket connection we fetch last 1000 trades from REST API (https://binance-docs.github.io/apidocs/delivery/en/#recent-trades-list) and store that info together with other captured WebSocket messages. Such messages are marked with "stream":"<symbol>@recentTrades" and "generated":true fields and data field has the same format as REST API response.

​

Market data collection details

​Market data collection infrastructure for Binance Delivery Futures is located in GCP asia-northeast1 (Tokyo, Japan). Real-time market data is captured via multiple WebSocket connections.

​

​

​