Binance US
Binance US historical market data details - currency pairs, data coverage and data collection specifics
Last updated
Binance US historical market data details - currency pairs, data coverage and data collection specifics
Last updated
Binance US exchange historical data for all it's currency pairs is available since 2019-09-25.
Historical CSV datasets for the first day of each month are available to download without API key. See downloadable CSV files documentation.
data type | symbol | date | |
trades | BTCUSD | 2019-12-01 | |
incremental_book_L2 | BTCUSD | 2019-12-01 | |
quotes | BTCUSD | 2019-12-01 | |
trades | ETHUSD | 2020-03-01 | |
incremental_book_L2 | ETHUSD | 2020-03-01 |
Historical data format is the same as provided by real-time Binance US 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.
See Python client docs.
Click any channel below to see HTTP API response with historical data recorded for it.
aggTrade - available since 2019-11-19
depthSnapshot - generated channel with full order book snapshots
Binance US 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 (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.
Market data collection infrastructure for Binance US is located in GCP europe-west2 region (London, UK). Real-time market data is captured via multiple WebSocket connections.