Blockchain.com Python API Docs | dltHub
Build a Blockchain.com-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Blockchain.com's REST API requires a timestamp in UTC milliseconds. It offers functionalities like market data, balance info, and trades. The API also supports WebSocket for real-time updates. The REST API base URL is https://api.blockchain.com/v3/exchange and All requests require an API key for authentication, sent via the 'X-API-Token' header..
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 Blockchain.com data in under 10 minutes.
What data can I load from Blockchain.com?
Here are some of the endpoints you can load from Blockchain.com:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| tickers | /tickers | GET | Get information on all symbols | |
| symbols | /symbols | GET | Get information on all trading symbols | |
| l2_symbol | /l2/{symbol} | GET | Get level 2 order book data for a symbol | |
| l3_symbol | /l3/{symbol} | GET | Get level 3 order book data for a symbol | |
| orders | /orders | GET | Get all orders | |
| trades | /trades | GET | Get all trades | |
| fills | /fills | GET | Get all fills | |
| accounts | /accounts | GET | Get all accounts | |
| deposits | /deposits | GET | Get all deposits | |
| withdrawals | /withdrawals | GET | Get all withdrawals | |
| whitelist | /whitelist | GET | Get all whitelisted addresses | |
| unspent_outputs | /unspent_outputs | GET | unspent_outputs | Get unspent outputs for an address |
| balance | /balance?active=$address | GET | $address | Get balance for an address |
| latest_block | /latestblock | GET | Get the latest block information |
How do I authenticate with the Blockchain.com API?
Authentication is done by including an API key in the 'X-API-Token' header for every request.
1. Get your credentials
Please refer to the Blockchain.com website or your account dashboard to generate an API key. The documentation states that an API key is required and must be set via the X-API-Token header.
2. Add them to .dlt/secrets.toml
[sources.blockchain_com_source] api_key = "your_api_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 Blockchain.com 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 blockchain_com_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline blockchain_com_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset blockchain_com_data The duckdb destination used duckdb:/blockchain_com.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline blockchain_com_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 tickers and symbols from the Blockchain.com 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 blockchain_com_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.blockchain.com/v3/exchange", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "tickers", "endpoint": {"path": "tickers"}}, {"name": "symbols", "endpoint": {"path": "symbols"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="blockchain_com_pipeline", destination="duckdb", dataset_name="blockchain_com_data", ) load_info = pipeline.run(blockchain_com_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("blockchain_com_pipeline").dataset() sessions_df = data.tickers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM blockchain_com_data.tickers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("blockchain_com_pipeline").dataset() data.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 Blockchain.com 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 Blockchain.com?
Request dlt skills, commands, AGENT.md files, and AI-native context.