MEXC Spot

MEXC Spot historical market data details - currency pairs, data coverage and data collection specifics

MEXC Spot historical data for all its currency pairs is available since 2026-06-25.

https://api.tardis.dev/v1/exchanges/mexcapi.tardis.dev

See MEXC Spot 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
incremental_book_L2	BTCUSDT	2026-07-01	Download sample
trades	BTCUSDT	2026-07-01	Download sample
quotes	BTCUSDT	2026-07-01	Download sample
book_ticker	BTCUSDT	2026-07-01	Download sample

API Access and data format

Historical data format is the same as provided by MEXC Spot WebSocket API v3 Market Streams with addition of local timestamps. MEXC Spot WebSocket market data is delivered as Protocol Buffers messages; Tardis.dev stores the decoded JSON form. 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 can perform data normalization client-side.

Python

# pip install tardis-dev
import asyncio
from tardis_dev import Channel, replay

async def main():
    async for local_timestamp, message in replay(
        exchange="mexc",
        from_date="2026-07-01",
        to_date="2026-07-02",
        filters=[Channel(name="[e-mail]@10ms", symbols=["BTCUSDT"])],
        api_key="YOUR_API_KEY",
    ):
        # messages as provided by MEXC Spot real-time stream, decoded from protobuf to JSON
        print(message)

asyncio.run(main())

See Python client docs.

Node.js

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

const messages = replay({
  exchange: 'mexc',
  from: '2026-07-01',
  to: '2026-07-02',
  filters: [{ channel: '[e-mail]@10ms', symbols: ['BTCUSDT'] }],
  apiKey: 'YOUR_API_KEY'
});

// messages as provided by MEXC Spot real-time stream, decoded from protobuf to JSON
for await (const { localTimestamp, message } of messages) {
  console.log(localTimestamp, message);
}

See Node.js client docs.

cURL & HTTP API

curl --compressed -g 'https://api.tardis.dev/v1/data-feeds/mexc?from=2026-07-01&filters=[{"channel":"[e-mail]@10ms","symbols":["BTCUSDT"]}]&offset=0'

https://api.tardis.dev/v1/data-feeds/mexc?from=2026-07-01&filters=[{%22channel%22:[e-mail]@10ms%22,%22symbols%22:[%22BTCUSDT%22]}]&offset=0api.tardis.dev

Example API response for MEXC Spot historical market data request

See HTTP API docs.

cURL & tardis-machine

curl -g 'localhost:8000/replay?options={"exchange":"mexc","filters":[{"channel":"[e-mail]@10ms","symbols":["BTCUSDT"]}],"from":"2026-07-01","to":"2026-07-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

Websocket Market Streams | MEXC APIMEXC_Global

See MEXC Spot WebSocket API v3 Market Streams docs providing documentation for each captured channel's format

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

• [e-mail]@10ms Spot public trade executions stream

• [e-mail]@10ms Spot order book incremental updates stream

• [e-mail]@10ms Generated spot order book snapshots from REST API, up to 5000 levels. Snapshot messages are marked with "generated":true.

• [e-mail]@10ms Best bid and ask price and amount updates stream

Market data collection details

Market data collection infrastructure for MEXC Spot is located in GCP asia-northeast1 (Tokyo, Japan).

Real-time market data is captured via multiple WebSocket connections to wss://wbs-api.mexc.com/ws.

MEXC Spot servers are located in AWS ap-northeast-1 region (Tokyo, Japan).