# Binance Jersey

Binance Jersey exchange historical data for **all its currency pairs** is available since **2019-10-30** until **2020-11-10.**

{% embed url="<https://api.tardis.dev/v1/exchanges/binance-jersey>" %}
See Binance Jersey 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](https://docs.tardis.dev/downloadable-csv-files/overview).

| data type             | symbol | date       |                                                                                                               |
| --------------------- | ------ | ---------- | ------------------------------------------------------------------------------------------------------------- |
| incremental\_book\_L2 | BTCEUR | 2019-12-01 | [Download sample](https://datasets.tardis.dev/v1/binance-jersey/incremental_book_L2/2019/12/01/BTCEUR.csv.gz) |
| trades                | BTCEUR | 2019-12-01 | [Download sample](https://datasets.tardis.dev/v1/binance-jersey/trades/2019/12/01/BTCEUR.csv.gz)              |
| quotes                | BTCEUR | 2019-12-01 | [Download sample](https://datasets.tardis.dev/v1/binance-jersey/quotes/2019/12/01/BTCEUR.csv.gz)              |

### 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](https://docs.tardis.dev/downloadable-csv-files/overview) or official [client libs](https://docs.tardis.dev/api/quickstart) 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-jersey",
        from_date="2020-01-01",
        to_date="2020-01-02",
        filters=[Channel(name="depth", symbols=["btceur"])],
        api_key="YOUR_API_KEY",
    ):
        # messages as provided by Binance Jersey real-time stream
        print(message)

asyncio.run(main())
```

See [Python client docs](https://docs.tardis.dev/python-client/quickstart).
{% endtab %}

{% tab title="Node.js" %}

```javascript
// npm install tardis-dev
import { replay } from 'tardis-dev';

const messages = replay({
  exchange: 'binance-jersey',
  from: '2020-01-01',
  to: '2020-01-02',
  filters: [{ channel: 'depth', symbols: ['btceur'] }],
  apiKey: 'YOUR_API_KEY'
});

// messages as provided by Binance Jersey real-time stream
for await (const { localTimestamp, message } of messages) {
  console.log(localTimestamp, message);
}
```

See [Node.js client docs](https://docs.tardis.dev/node-client/quickstart).
{% endtab %}

{% tab title="cURL & HTTP API" %}

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

{% embed url="<https://api.tardis.dev/v1/data-feeds/binance-jersey?from=2020-01-01&filters=[{%22channel%22:%22depth%22,%22symbols%22:[%22btceur%22]}]&offset=0>" %}
Example API response for Binance Jersey historical market data request
{% endembed %}

See [HTTP API docs](https://docs.tardis.dev/api/http-api-reference).
{% endtab %}

{% tab title="cURL & tardis-machine" %}

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

[Tardis-machine](https://docs.tardis.dev/tardis-machine/quickstart) is a locally runnable server that exposes API allowing efficiently requesting historical market data for whole time periods in contrast to [HTTP API](https://docs.tardis.dev/api/http-api-reference) that provides data only in minute by minute slices.

See [tardis-machine](https://docs.tardis.dev/tardis-machine/quickstart) docs.
{% endtab %}
{% endtabs %}

### Captured real-time channels

{% embed url="<https://github.com/binance-jersey/binance-official-api-docs>" %}
See Binance Jersey WebSocket API docs providing documentation for each captured channel's format
{% endembed %}

{% hint style="info" %}
Click any channel below to see [HTTP API](https://docs.tardis.dev/api/http-api-reference#data-feeds-exchange) response with historical data recorded for it.
{% endhint %}

* [trade](https://api.tardis.dev/v1/data-feeds/binance-jersey?from=2020-03-01\&filters=\[{%22channel%22:%22trade%22}]) — available since **2020-01-30**, available until **2020-11-03** Public spot trade executions stream
* [depth](https://api.tardis.dev/v1/data-feeds/binance-jersey?from=2020-06-01\&filters=\[{%22channel%22:%22depth%22}]) Incremental order book updates stream subscribed as @depth\@100ms
* [depthSnapshot](https://api.tardis.dev/v1/data-feeds/binance-jersey?from=2020-06-01\&filters=\[{%22channel%22:%22depthSnapshot%22}]) — *generated* Generated full order book snapshots stream

  Binance Jersey real-time WebSocket API did not provide initial order book snapshots. To overcome this issue we fetched initial order book snapshots from REST API and stored them together with the rest of the WebSocket messages (top 1000 levels). Snapshot messages were marked with `"stream":"<symbol>@depthSnapshot"` and `"generated":true`.

  During data collection, integrity of incremental order book updates was validated using sequence numbers from the real-time feed (`U` and `u` fields). If a missed message was detected, the WebSocket connection was restarted. Initial book snapshots fetched from REST API were also validated for overlap with received `depth` messages.
* [aggTrade](https://api.tardis.dev/v1/data-feeds/binance-jersey?from=2020-03-01\&filters=\[{%22channel%22:%22aggTrade%22}]) — available since **2020-01-30**, available until **2020-11-03** Aggregated spot trade executions stream
* [ticker](https://api.tardis.dev/v1/data-feeds/binance-jersey?from=2020-06-01\&filters=\[{%22channel%22:%22ticker%22}]) 24h spot ticker updates stream
* [bookTicker](https://api.tardis.dev/v1/data-feeds/binance-jersey?from=2020-06-01\&filters=\[{%22channel%22:%22bookTicker%22}]) Best bid and best ask updates stream

### Market data collection details

[Market data collection infrastructure](https://docs.tardis.dev/faq/general#what-is-your-infrastructure-setup) for Binance Jersey was located in GCP europe-west2 region (London, UK).

Real-time market data is captured via **single WebSocket connection** to `wss://stream.binance.je:9443`.

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