Bitget Python API Docs | dltHub
Build a Bitget-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Bitget's REST API documentation is available at https://bitgetlimited.github.io/apidoc/en/spot/. It includes official API endpoints for trading on the spot market. The API requires API keys for authentication. The REST API base URL is https://api.bitget.com and All private endpoints require API key HMAC‑SHA256 signature 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 Bitget data in under 10 minutes.
What data can I load from Bitget?
Here are some of the endpoints you can load from Bitget:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| spot_time | /api/spot/v1/public/time | GET | data | Server time (single value in data) |
| spot_products | /api/spot/v1/public/products | GET | data | All spot trading pairs (array in data) |
| spot_product | /api/spot/v1/public/product | GET | data | Single product details (array in data) |
| spot_ticker | /api/spot/v1/market/ticker | GET | data | Single ticker (object in data) |
| spot_tickers | /api/spot/v1/market/tickers | GET | data | All tickers (array in data) |
| spot_fills | /api/spot/v1/market/fills | GET | data | Recent trades/fills (array in data) |
| spot_candles | /api/spot/v1/market/candles | GET | data | OHLC candle array (data is array) |
| spot_depth | /api/spot/v1/market/depth | GET | data | Orderbook with asks/bids under data (object) |
| mix_ticker | /api/mix/v1/market/ticker | GET | data | Single contract ticker (object in data) |
| mix_tickers | /api/mix/v1/market/tickers | GET | data | All contract tickers (array in data) |
| mix_candles | /api/mix/v1/market/candles | GET | Candles endpoint returns top‑level JSON array for historic candles | |
| account_assets | /api/spot/v1/account/assets | GET | data | Account assets (array in data) – private endpoint requiring signature |
| wallet_deposit_address | /api/spot/v1/wallet/deposit-address | GET | data | Deposit address (data object) – private endpoint |
How do I authenticate with the Bitget API?
Bitget uses API key + secret to sign requests. Include headers ACCESS-KEY (api key), ACCESS-SIGN (base64 HMAC‑SHA256 of pre‑hash string), ACCESS-TIMESTAMP (milliseconds), and ACCESS-PASSPHRASE (passphrase).
1. Get your credentials
- Log in to Bitget web (Personal Center). 2) Go to API Management (Create New API). 3) Provide a note, set permissions (read‑only/spot_trade/contract_trade etc.), whitelist IPs if desired. 4) Save — you'll receive ACCESS-KEY (api key), SECRET (secret key) and PASS‑PHRASE; record the secret immediately as it is shown only once.
2. Add them to .dlt/secrets.toml
[sources.bitget_source] api_key = "your_api_key_here" secret = "your_api_secret_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 Bitget 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 bitget_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline bitget_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset bitget_data The duckdb destination used duckdb:/bitget.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline bitget_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 spot_tickers and spot_products from the Bitget 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 bitget_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.bitget.com", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "spot_tickers", "endpoint": {"path": "api/spot/v1/market/tickers", "data_selector": "data"}}, {"name": "spot_products", "endpoint": {"path": "api/spot/v1/public/products", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bitget_pipeline", destination="duckdb", dataset_name="bitget_data", ) load_info = pipeline.run(bitget_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("bitget_pipeline").dataset() sessions_df = data.spot_products.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM bitget_data.spot_products LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("bitget_pipeline").dataset() data.spot_products.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 Bitget 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 Bitget?
Request dlt skills, commands, AGENT.md files, and AI-native context.