BlockCypher Ethereum API Python API Docs | dltHub
Build a BlockCypher Ethereum API-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
BlockCypher Ethereum API provides RESTful services for blockchain transactions and contract interactions. It includes endpoints for sending transactions and decoding raw transaction data. The API supports smart contract deployment and management. The REST API base URL is https://api.blockcypher.com/v1/eth and Read‑only GET calls do not require a token; a token is optional for higher rate limits..
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 BlockCypher Ethereum API data in under 10 minutes.
What data can I load from BlockCypher Ethereum API?
Here are some of the endpoints you can load from BlockCypher Ethereum API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| chain | /v1/eth/main | GET | General blockchain information | |
| block | /v1/eth/main/blocks/{block_hash} | GET | Detailed block information | |
| address | /v1/eth/main/addrs/{address} | GET | txrefs | List of transaction references for an address |
| hooks | /v1/eth/main/hooks | GET | List of registered webhooks | |
| contracts | /v1/eth/main/contracts | GET | results | List of contracts and their details |
How do I authenticate with the BlockCypher Ethereum API API?
Authentication is performed by adding a token query parameter to the request URL; no additional headers are needed.
1. Get your credentials
- Visit https://accounts.blockcypher.com and create a developer account.
- After verifying your email, log in to the dashboard.
- Navigate to the API Tokens section.
- Click "Create Token" and give it a name.
- Copy the generated token; you will use it as the
tokenquery parameter in API calls.
2. Add them to .dlt/secrets.toml
[sources.blockcypher_ethereum_api_source] token = "your_token_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 BlockCypher Ethereum API 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 blockcypher_ethereum_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline blockcypher_ethereum_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset blockcypher_ethereum_api_data The duckdb destination used duckdb:/blockcypher_ethereum_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline blockcypher_ethereum_api_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 address and block from the BlockCypher Ethereum API 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 blockcypher_ethereum_api_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.blockcypher.com/v1/eth", "auth": { "type": "api_key", "token": token, }, }, "resources": [ {"name": "address", "endpoint": {"path": "addrs/{address}", "data_selector": "txrefs"}}, {"name": "block", "endpoint": {"path": "blocks/{block_hash}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="blockcypher_ethereum_api_pipeline", destination="duckdb", dataset_name="blockcypher_ethereum_api_data", ) load_info = pipeline.run(blockcypher_ethereum_api_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("blockcypher_ethereum_api_pipeline").dataset() sessions_df = data.address.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM blockcypher_ethereum_api_data.address LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("blockcypher_ethereum_api_pipeline").dataset() data.address.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 BlockCypher Ethereum API 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 BlockCypher Ethereum API?
Request dlt skills, commands, AGENT.md files, and AI-native context.