OKX Spot
OKX Spot historical market data details - currency pairs, data coverage and data collection specifics
OKEx historical data for spot high caps currency pairs is available since 2019-03-30, data for all spot currency pairs is available since 2021-03-11.
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
How to download all OKEx datasets for all instruments
See full downloadable CSV files documentation with datasets format spec, data samples and more.
See docs that shows all available download options (download path customization, filenames conventions and more).
See docs that shows all available download options (download path customization, filenames conventions and more).
See datasets API reference which allows downloading single file at once.
API Access and data format
Historical data format is the same as provided by real-time OKX WebSocket v3 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 or official client libs that can perform data normalization client-side.
See Python client docs.
See Node.js client docs.
See HTTP API docs.
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
spot/depth - available until 2020-04-10
spot/depth_l2_tbt - available since 2020-04-10
system/status - available since 2020-07-05
Market data collection details
Market data collection infrastructure for OKX Spot since 2022-05-04T16:45 is located in AWS HK region (Hong Kong, China, VPC colo setup), before that, starting since 2020-05-15 it was located in GCP asia-northeast1 (Tokyo, Japan) and initially it was located in GCP europe-west2 region (London, UK). Real-time market data is captured via multiple WebSocket connections.
Last updated