# Upbit

Upbit exchange historical data for **all its currency pairs** is available since **2021-03-03**.

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

| data type             | symbol  | date       |                                                                                                       |
| --------------------- | ------- | ---------- | ----------------------------------------------------------------------------------------------------- |
| incremental\_book\_L2 | KRW-BTC | 2021-09-01 | [Download sample](https://datasets.tardis.dev/v1/upbit/incremental_book_L2/2021/09/01/KRW-BTC.csv.gz) |
| trades                | KRW-BTC | 2021-09-01 | [Download sample](https://datasets.tardis.dev/v1/upbit/trades/2021/09/01/KRW-BTC.csv.gz)              |
| quotes                | KRW-BTC | 2021-09-01 | [Download sample](https://datasets.tardis.dev/v1/upbit/quotes/2021/09/01/KRW-BTC.csv.gz)              |

### API Access and data format

Historical data format is the same as provided by real-time Upbit WebSocket **Market Data API v1** (<wss://api.upbit.com/websocket/v1>) 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](/downloadable-csv-files/overview.md) or official [client libs](/api/quickstart.md) that can 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="upbit",
        from_date="2024-01-01",
        to_date="2024-01-02",
        filters=[Channel(name="orderbook", symbols=["KRW-BTC"])],
        api_key="YOUR_API_KEY",
    ):
        # messages as provided by Upbit real-time stream
        print(message)

asyncio.run(main())
```

See [Python client docs](/python-client/quickstart.md).
{% endtab %}

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

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

const messages = replay({
  exchange: 'upbit',
  from: '2024-01-01',
  to: '2024-01-02',
  filters: [{ channel: 'orderbook', symbols: ['KRW-BTC'] }],
  apiKey: 'YOUR_API_KEY'
});

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

See [Node.js client docs](/node-client/quickstart.md).
{% endtab %}

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

```bash
curl --compressed -g 'https://api.tardis.dev/v1/data-feeds/upbit?from=2024-01-01&filters=[{"channel":"orderbook","symbols":["KRW-BTC"]}]&offset=0'
```

{% embed url="<https://api.tardis.dev/v1/data-feeds/upbit?from=2024-01-01&filters=[{%22channel%22:%22orderbook%22,%22symbols%22:[%22KRW-BTC%22]}]&offset=0>" %}
Example API response for Upbit historical market data request
{% endembed %}

See [HTTP API docs](/api/http-api-reference.md).
{% endtab %}

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

```bash
curl -g 'localhost:8000/replay?options={"exchange":"upbit","filters":[{"channel":"orderbook","symbols":["KRW-BTC"]}],"from":"2024-01-01","to":"2024-01-02"}'
```

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

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

### Captured real-time channels

{% embed url="<https://docs.upbit.com/kr/reference/websocket-guide>" %}
See Upbit WebSocket API docs providing documentation for each captured channel's format
{% endembed %}

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

* [trade](https://api.tardis.dev/v1/data-feeds/upbit?from=2024-01-01\&filters=\[{%22channel%22:%22trade%22}]) Public trade executions stream
* [orderbook](https://api.tardis.dev/v1/data-feeds/upbit?from=2024-01-01\&filters=\[{%22channel%22:%22orderbook%22}]) Order book snapshots and unit updates
* [ticker](https://api.tardis.dev/v1/data-feeds/upbit?from=2024-01-01\&filters=\[{%22channel%22:%22ticker%22}]) 24h ticker updates

### Market data collection details

[Market data collection infrastructure](/faq/general.md#what-is-your-infrastructure-setup) for Upbit is located in GCP asia-northeast1 (Tokyo, Japan).

Real-time market data is captured via **multiple WebSocket connections** to <wss://api.upbit.com/websocket/v1>.

{% hint style="info" %}
Upbit servers are located in AWS ap-northeast-2 region (Seoul, South Korea).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tardis.dev/historical-data-details/upbit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.