Blockchair Python API Docs | dltHub

Build a Blockchair-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Blockchair is a multi-blockchain explorer and data API providing unified access to on-chain data across multiple blockchains. The REST API base URL is https://api.blockchair.com and all requests support an optional API key query parameter.

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 add "dlt[hub]" and start loading Blockchair data in under 10 minutes.


What data can I load from Blockchair?

Here are some of the endpoints you can load from Blockchair:

ResourceEndpointMethodData selectorDescription
blocks_query/{chain}/blocksGETdataSQL-like query interface for blocks
transactions_query/{chain}/transactionsGETdataSQL-like query interface for transactions
addresses_query/{chain}/addressesGETdataSQL-like query interface for addresses
outputs_query/{chain}/outputsGETdataSQL-like query interface for outputs
raw_block/{chain}/raw/block/{id}GETdataRaw node-level block data
raw_transaction/{chain}/raw/transaction/{hash}GETdataRaw node-level transaction data

How do I authenticate with the Blockchair API?

Authentication is performed by appending an API key as a query parameter named 'key' to the request URL, for example: ?key=YOUR_API_KEY. Requests without a key are permitted for personal or testing use with specific daily limits.

1. Get your credentials

To obtain a Blockchair API key: 1. Visit the pricing page (https://blockchair.com/api/plans) to choose a suitable plan (or the free testing tier). 2. Upon purchase or selection, you will receive a one-time password or activation instructions. 3. Navigate to the Premium API dashboard at https://api.blockchair.com/premium. 4. Enter your one-time password in the 'I want to activate an API key I've just purchased...' form and complete the requested details to generate your API key. For non-commercial or academic use, you may also contact info@blockchair.com directly.

2. Add them to .dlt/secrets.toml

[sources.blockchair_source] blockchair_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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Blockchair 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:

uv run python blockchair_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline blockchair_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset blockchair_data The duckdb destination used duckdb:/blockchair.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub 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 /

/blocks and /
/transactions from the Blockchair 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 blockchair_source(key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.blockchair.com", "auth": {"type": "api_key", "api_key": key, "name": "key", "location": "query"}, }, "resources": [ {"name": "blocks_query", "endpoint": {"path": "{chain}/blocks", "data_selector": "data"}}, {"name": "transactions_query", "endpoint": {"path": "{chain}/transactions", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="blockchair_pipeline", destination="duckdb", dataset_name="blockchair_data", ) load_info = pipeline.run(blockchair_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("blockchair_pipeline").dataset() sessions_df = data.blocks_query.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM blockchair_data.blocks_query LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("blockchair_pipeline").dataset() data.blocks_query.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 Blockchair data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Blockchair?

Request dlt skills, commands, AGENT.md files, and AI-native context.