Each row is a public trade print as published by the exchange; trade ID semantics and aggregation behavior vary by venue.
BitMEX Trade Dataset
BitMEX Historical Trade Data
BitMEX trade prints from futures markets, normalized into the same tick schema used across CryptoHFTData venues.
Coverage
Trade data coverage
Coverage is organized by exchange, market type, and hourly object path. Live symbol counts are shown when the symbols API responds during page generation.
| Venue | Exchange ID | Market | History start | Trade symbols |
|---|---|---|---|---|
| BitMEX | bitmex | Futures | 2025-09-29 | 146 |
Schema
Normalized trade schema
Every trade row is a tick-level execution with exchange timing, trade ID, price, quantity, maker/taker direction, and order type.
| Field | Type | Nullable | Description |
|---|---|---|---|
| received_time | INT64 | No | Unix timestamp (nanoseconds) when our system received the trade event |
| event_time | INT64 | No | Unix timestamp (exchange dependent on timescale) when the exchange generated the event |
| symbol | STRING | No | Trading pair symbol (e.g., 'BTCUSDT') |
| trade_id | INT64 | No | Exchange-specific unique trade identifier |
| price | STRING | No | Trade execution price (stored as string for precision) |
| quantity | STRING | No | Trade quantity/volume (stored as string for precision) |
| trade_time | INT64 | No | Unix timestamp (exchange dependent on timescale) when the trade occurred |
| is_buyer_maker | BOOLEAN | No | True if buyer was the maker (passive side), false if taker |
| order_type | STRING | No | Type of order that generated this trade (e.g., "LIMIT", "MARKET") |
Access
Download with Python or REST
The sample below downloads XBTUSDT from BitMEX for 2025-09-29, hour 20.
import cryptohftdata as chd
client = chd.CryptoHFTDataClient(api_key="your-api-key-here")
df = client.get_trades(
symbol="XBTUSDT",
exchange=chd.exchanges.BITMEX,
start_date="2025-09-29",
end_date="2025-09-29",
)
print(df.head())
print(f"Trades: {len(df):,}")curl "https://api.cryptohftdata.com/download?file=bitmex/2025-09-29/20/XBTUSDT_trades.parquet.zst&api_key=your-api-key-here" \
-o XBTUSDT_trades_20.parquet.zstCaveats
What this data is and is not
These details are important for accurate backtests, replay pipelines, and microstructure features.
Prices and quantities are stored as strings to preserve exchange precision; cast to decimals or floats as needed.
This page starts on 2025-09-29 based on the earliest stored hourly files for its covered exchange IDs and grows as new hourly files are published.
Next
Use the trade data
Start with an API key, then move between docs, tutorials, and the browser data explorer as needed.