Binance US
Binance US historical market data details - currency pairs, data coverage and data collection specifics
Binance US exchange historical data for all it's currency pairs is available since 2019-09-25.
https://api.tardis.dev/v1/exchanges/binance-us
api.tardis.dev
See Binance US historical data coverage: available symbols, channels, date ranges and incidents
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.
Python
Node.js
cURL & HTTP API
cURL & tardis-machine
# 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-us",
from_date="2019-12-01",
to_date="2019-12-02",
filters=[Channel(name="depth", symbols=["bnbusd"])]
)
# messages as provided by Binance US 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-us',
from: '2019-12-01',
to: '2019-12-02',
filters: [{ channel: 'depth', symbols: ['bnbusd'] }],
apiKey: 'YOUR_API_KEY'
});
// messages as provided by Binance US 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-us?from=2019-12-01&filters=[{"channel":"depth","symbols":["bnbusd"]}]&offset=0'
https://api.tardis.dev/v1/data-feeds/binance-us?from=2019-12-01&filters=[{%22channel%22:%22depth%22,%22symbols%22:[%22bnbusd%22]}]&offset=0
api.tardis.dev
Example API response for Binance US historical market data request
curl -g 'localhost:8000/replay?options={"exchange":"binance-us","filters":[{"channel":"depth","symbols":["bnbusd"]}],"from":"2019-12-01","to":"2019-12-02"}'
Tardis-machine is a locally runnable server that exposes API allowing efficiently requesting historical market data for whole time periods in contrast to HTTP API that provides data only in minute by minute slices.
GitHub - binance-us/binance-official-api-docs: Official Documentation for the Binance US APIs and Streams
GitHub
See Binance US WebSocket API docs providing documentation for each captured channel's format
- 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":truefields.During data collection integrity of order book incremental updates is being validated using sequence numbers provided by real-time feed (Uandufields) - in case of detecting missed message WebSocket connection is being restarted. We also validate if initial book snapshot fetched from REST API overlaps with receiveddepthmessages.
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.
Last modified 9d ago