OKX Python API Docs | dltHub
Build a OKX-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
OKX API v5 supports REST and WebSocket for order management, with endpoints like /api/v5/trade/order for placing orders and /api/v5/account/positions for position details. API keys are required for authentication, and rate limits apply per sub-account. For more details, refer to the official OKX API documentation. The REST API base URL is https://www.okx.com/api/v5 and HMAC-SHA256 signed requests using API key, secret and passphrase (OK-ACCESS headers).
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading OKX data in under 10 minutes.
What data can I load from OKX?
Here are some of the endpoints you can load from OKX:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| market_tickers | /api/v5/market/tickers | GET | data | Latest price snapshot and 24h stats for multiple instruments |
| market_ticker | /api/v5/market/ticker | GET | data | Latest price snapshot for a single instrument |
| market_candles | /api/v5/market/candles | GET | (top-level array) | Candlestick (kline) data for an instrument |
| market_history_candles | /api/v5/market/history-candles | GET | (top-level array) | Historical candlestick data across longer ranges |
| market_depth | /api/v5/market/books | GET | data | Order book (depth) for an instrument |
| public_instruments | /api/v5/public/instruments | GET | data | List of tradable instruments and their metadata |
| account_balance | /api/v5/account/balance | GET | data | Account balances (private; requires auth) |
| asset_exchange_list | /api/v5/asset/exchange-list | GET | data | Public list of exchanges for funding account transfers |
| market_ticker_index | /api/v5/market/index-tickers | GET | data | Index ticker data |
| market_mark_price_candles | /api/v5/market/mark-price-candles | GET | (top-level array) | Mark-price candlesticks |
How do I authenticate with the OKX API?
Private endpoints require four headers: OK-ACCESS-KEY (API key), OK-ACCESS-SIGN (Base64 HMAC-SHA256 of timestamp+method+requestPath+body using SecretKey), OK-ACCESS-TIMESTAMP (ISO8601 with milliseconds), and OK-ACCESS-PASSPHRASE (your API passphrase). GET query parameters are included in the requestPath when signing.
1. Get your credentials
- Log into OKX web dashboard. 2) Navigate to API -> Create API Key. 3) Choose label, permissions and (optionally) IP whitelist. 4) Save the generated API Key, Secret Key and Passphrase securely (SecretKey shown only once). 5) Use the API Key, SecretKey and Passphrase to build OK-ACCESS headers when signing requests.
2. Add them to .dlt/secrets.toml
[sources.okx_source] api_key = "your_api_key_here" secret_key = "your_secret_key_here" passphrase = "your_passphrase_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the OKX API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python okx_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline okx_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset okx_data The duckdb destination used duckdb:/okx.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline okx_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads market_tickers and public_instruments from the OKX API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def okx_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.okx.com/api/v5", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "market_tickers", "endpoint": {"path": "api/v5/market/tickers", "data_selector": "data"}}, {"name": "public_instruments", "endpoint": {"path": "api/v5/public/instruments", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="okx_pipeline", destination="duckdb", dataset_name="okx_data", ) load_info = pipeline.run(okx_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("okx_pipeline").dataset() sessions_df = data.market_tickers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM okx_data.market_tickers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("okx_pipeline").dataset() data.market_tickers.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load OKX data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for OKX?
Request dlt skills, commands, AGENT.md files, and AI-native context.