Binance Jersey

Binance Jersey historical market data details - currency pairs, data coverage and data collection specifics

Binance Jersey exchange historical data for all it's currency pairs is available since 2019-10-30.

See Binance Jersey historical data coverage: available symbols, channels, date ranges and incidents

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.

data type

symbol

date

trades

BTCEUR

2019-12-01

Download sample

incremental_book_L2

BTCEUR

2019-12-01

Download sample

quotes

BTCEUR

2019-12-01

Download sample

trades

ETHEUR

2020-03-01

Download sample

incremental_book_L2

ETHEUR

2020-03-01

Download sample

API Access and data format

Historical data format is the same as provided by real-time Binance Jersey 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
Python
# 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-jersey",
from_date="2019-12-01",
to_date="2019-12-02",
filters=[Channel(name="depth", symbols=["btcgbp"])]
)
# messages as provided by Binance Jersey real-time stream
async for local_timestamp, message in messages:
print(message)
asyncio.run(replay())

See Python client docs.

Node.js
// npm install tardis-dev
const { replay } = require('tardis-dev');
async function run() {
try {
const messages = replay({
exchange: 'binance-jersey',
from: '2019-12-01',
to: '2019-12-02',
filters: [{ channel: 'depth', symbols: ['btcgbp'] }],
apiKey: 'YOUR_API_KEY'
});
// messages as provided by Binance Jersey real-time stream
for await (const { localTimestamp, message } of messages) {
console.log(localTimestamp, message);
}
} catch (e) {
console.error(e);
}
}
run();

See Node.js client docs.

cURL & HTTP API
curl -g 'https://api.tardis.dev/v1/data-feeds/binance-jersey?from=2019-12-01&filters=[{"channel":"depth","symbols":["btcgbp"]}]&offset=0'

See HTTP API docs.

cURL & tardis-machine
curl -g 'localhost:8000/replay?options={"exchange":"binance-jersey","filters":[{"channel":"depth","symbols":["btcgbp"]}],"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.

See tardis-machine docs.

Captured real-time channels

Click any channel below to see HTTP API response with historical data recorded for it.

  • trade

  • aggTrade - available since 2019-11-19

  • ticker

  • depth

  • depthSnapshot - generated channel with full order book snapshots Binance Jersey 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.

  • recentTrades - generated channel, available since 2020-05-19 After establishing successful real-time WebSocket connection we fetch last 1000 trades from REST API 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 Jersey is located in GCP europe-west2 region (London, UK). Real-time market data is captured via single WebSocket connection.