# Crypto.com Crypto.com exchange historical data for **all its instruments** is available since **2022-06-01**. {% embed url="" %} See Crypto.com exchange 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 | BTCUSD-PERP | 2023-03-01 | [Download sample](https://datasets.tardis.dev/v1/crypto-com/incremental_book_L2/2023/03/01/BTCUSD-PERP.csv.gz) | | trades | BTCUSD-PERP | 2023-03-01 | [Download sample](https://datasets.tardis.dev/v1/crypto-com/trades/2023/03/01/BTCUSD-PERP.csv.gz) | | derivative\_ticker | BTCUSD-PERP | 2023-03-01 | [Download sample](https://datasets.tardis.dev/v1/crypto-com/derivative_ticker/2023/03/01/BTCUSD-PERP.csv.gz) | ### API Access and data format Historical data format is the same as provided by real-time Crypto.com Exchange WebSocket **Market Data API 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="crypto-com", from_date="2024-01-01", to_date="2024-01-02", filters=[Channel(name="book", symbols=["BTCUSD-PERP"])], api_key="YOUR_API_KEY", ): # messages as provided by Crypto.com exchange 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: 'crypto-com', from: '2024-01-01', to: '2024-01-02', filters: [{ channel: 'book', symbols: ['BTCUSD-PERP'] }], apiKey: 'YOUR_API_KEY' }); // messages as provided by Crypto.com exchange 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/crypto-com?from=2024-01-01&filters=[{"channel":"book","symbols":["BTCUSD-PERP"]}]&offset=0' ``` {% embed url="" %} Example API response for Crypto.com exchange 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":"crypto-com","filters":[{"channel":"book","symbols":["BTCUSD-PERP"]}],"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="" %} See Crypto.com exchange 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/crypto-com?from=2024-01-01\&filters=\[{%22channel%22:%22trade%22}]) Trade executions stream * [book](https://api.tardis.dev/v1/data-feeds/crypto-com?from=2024-01-01\&filters=\[{%22channel%22:%22book%22}]) Order book snapshots and updates stream with 5s heartbeat when unchanged * [ticker](https://api.tardis.dev/v1/data-feeds/crypto-com?from=2024-01-01\&filters=\[{%22channel%22:%22ticker%22}]) Best bid/ask, last price and 24h stats stream * [index](https://api.tardis.dev/v1/data-feeds/crypto-com?from=2024-01-01\&filters=\[{%22channel%22:%22index%22}]) — available since **2022-11-02** Index price updates stream * [mark](https://api.tardis.dev/v1/data-feeds/crypto-com?from=2024-01-01\&filters=\[{%22channel%22:%22mark%22}]) — available since **2022-11-02** Mark price updates stream * [funding](https://api.tardis.dev/v1/data-feeds/crypto-com?from=2024-01-01\&filters=\[{%22channel%22:%22funding%22}]) — available since **2022-11-01** Funding rate updates stream * [estimatedfunding](https://api.tardis.dev/v1/data-feeds/crypto-com?from=2025-01-01\&filters=\[{%22channel%22:%22estimatedfunding%22}]) Estimated funding rate updates stream * [settlement](https://api.tardis.dev/v1/data-feeds/crypto-com?from=2025-01-01\&filters=\[{%22channel%22:%22settlement%22}]) — available since **2022-11-01** Settlement price and event updates stream ### Market data collection details [Market data collection infrastructure](/faq/general.md#what-is-your-infrastructure-setup) for Crypto.com exchange is located in GCP asia-northeast1 (Tokyo, Japan). Real-time market data is captured via **multiple WebSocket connections** to `wss://stream.crypto.com/exchange/v1/market` (proxied via Cloudflare). {% hint style="info" %} Crypto.com exchange servers are located in AWS ap-northeast-1 region (Tokyo, Japan). {% 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/crypto-com.md?ask= ``` 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.