Bithumb Futures Python API Docs | dltHub
Build a Bithumb Futures-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
To retrieve data from Bithumb Futures API, use the official documentation at https://bithumbfutures.github.io/bithumb-futures-api-doc/. For funding rate, check the REST API documentation for available endpoints. JSONDecodeError indicates a response with no content. The REST API base URL is https://bithumbfutures.com/ and All private requests require HMAC-SHA256 authentication using an API key, timestamp, and a generated signature..
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 Bithumb Futures data in under 10 minutes.
What data can I load from Bithumb Futures?
Here are some of the endpoints you can load from Bithumb Futures:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| market_data | /api/pro/v1/futures/market-data | GET | Market Data | |
| order_book | /api/pro/v1/futures/market-data/order-book | GET | data.data | Order Book (Depth) Data |
| ticker_one_product | /api/pro/v1/futures/market-data/ticker | GET | data | Ticker for one product |
| list_of_tickers | /api/pro/v1/futures/market-data/tickers | GET | data | List of Tickers |
| collateral_balance | /api/pro/v1/futures/collateral-balance | GET | Collateral Balance | |
| open_orders | /api/pro/v1/futures/order/open | GET | data | Open Orders |
How do I authenticate with the Bithumb Futures API?
To access private data, requests must include x-auth-key (API key), x-auth-timestamp (UTC timestamp in milliseconds), and x-auth-signature headers. The signature is generated by HMAC-SHA256 hashing a message constructed from the secret key, timestamp, and request path.
1. Get your credentials
Instructions for obtaining API credentials from the Bithumb Futures dashboard are not available in the provided documentation.
2. Add them to .dlt/secrets.toml
[sources.bithumb_futures_source] api_key = "your_api_key_here" api_secret = "your_api_secret_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 Bithumb Futures 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 bithumb_futures_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline bithumb_futures_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset bithumb_futures_data The duckdb destination used duckdb:/bithumb_futures.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline bithumb_futures_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 list_of_tickers and collateral_balance from the Bithumb Futures 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 bithumb_futures_source(api_key, api_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://bithumbfutures.com/", "auth": { "type": "hmac", "api_key, api_secret": api_key, api_secret, }, }, "resources": [ {"name": "list_of_tickers", "endpoint": {"path": "api/pro/v1/futures/market-data/tickers", "data_selector": "data"}}, {"name": "collateral_balance", "endpoint": {"path": "api/pro/v1/futures/collateral-balance"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bithumb_futures_pipeline", destination="duckdb", dataset_name="bithumb_futures_data", ) load_info = pipeline.run(bithumb_futures_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("bithumb_futures_pipeline").dataset() sessions_df = data.list_of_tickers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM bithumb_futures_data.list_of_tickers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("bithumb_futures_pipeline").dataset() data.list_of_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 Bithumb Futures 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 Bithumb Futures?
Request dlt skills, commands, AGENT.md files, and AI-native context.