CoinEx Python API Docs | dltHub
Build a CoinEx-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
CoinEx API documentation is available at https://docs.coinex.com/api/v2/ for detailed integration and interaction with the exchange. The guide at https://docs.coinex.com/api/v2/guide offers a quick start for API services. GitHub documentation at https://coinexcom.github.io/coinex_api_en_doc/ covers trading functions and market data endpoints. The REST API base URL is https://api.coinex.com/v2 and API key (access_id) + secret key HMAC signature required for signed endpoints.
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 CoinEx data in under 10 minutes.
What data can I load from CoinEx?
Here are some of the endpoints you can load from CoinEx:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| market_list | market/list | GET | data | List of market objects |
| market_ticker | market/ticker | GET | data | Ticker (latest price) for market(s) |
| market_depth | market/depth | GET | data | Order book depth for a market |
| market_trades | market/trades | GET | data | Latest trades for a market |
| market_kline | market/kline | GET | data | K-line / candlestick data |
| account_balance | balance/info | GET | data | Account balance info (signed) |
| order_pending | order/pending | GET | data | User pending orders (signed) |
| order_status | order/status | GET | data | Query order status (signed) |
| common_maintain | common/maintain/info | GET | data | Site-wide maintenance info |
| common_temp_maintain | common/temp-maintain/info | GET | data | Partial maintenance info |
How do I authenticate with the CoinEx API?
CoinEx uses an API key (access_id) and secret_key. For signed endpoints you must include a signature header generated by signing the sorted request parameters with the secret_key; public market endpoints do not require a signature.
1. Get your credentials
- Sign in to your CoinEx account. 2) Open API Management / API Key page (https://www.coinex.com/en/apikey). 3) Create a new API key and note the access_id and secret_key. 4) Set permissions and IP restrictions as needed; keep secret_key safe.
2. Add them to .dlt/secrets.toml
[sources.coinex_p2p_source] access_id = "your_access_id_here" secret_key = "your_secret_key_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 CoinEx 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 coinex_p2p_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline coinex_p2p_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset coinex_p2p_data The duckdb destination used duckdb:/coinex_p2p.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline coinex_p2p_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/ticker and market/depth from the CoinEx 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 coinex_p2p_source(access_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.coinex.com/v2", "auth": { "type": "api_key", "access_id": access_id, }, }, "resources": [ {"name": "market_ticker", "endpoint": {"path": "market/ticker", "data_selector": "data"}}, {"name": "market_depth", "endpoint": {"path": "market/depth", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="coinex_p2p_pipeline", destination="duckdb", dataset_name="coinex_p2p_data", ) load_info = pipeline.run(coinex_p2p_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("coinex_p2p_pipeline").dataset() sessions_df = data.market_ticker.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM coinex_p2p_data.market_ticker LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("coinex_p2p_pipeline").dataset() data.market_ticker.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 CoinEx 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 CoinEx?
Request dlt skills, commands, AGENT.md files, and AI-native context.