Bitquery Python API Docs | dltHub
Build a Bitquery-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Bitquery's REST API allows querying blockchain transaction data, including details like block height and timestamps. The API supports filtering by transaction hash and address. The latest documentation is available at https://docs.bitquery.io/v1/. The REST API base URL is https://graphql.bitquery.io/ and All requests require a Bearer token (API access token) in the Authorization 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 Bitquery data in under 10 minutes.
What data can I load from Bitquery?
Here are some of the endpoints you can load from Bitquery:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| transactions | (GraphQL POST) root field EVM.Transactions | POST | data.EVM.Transactions | Query transaction lists across supported EVM chains. |
| calls | (GraphQL POST) root field EVM.Calls | POST | data.EVM.Calls | Retrieve internal call details for smart‑contract interactions. |
| bitcoin_transactions | (GraphQL POST) root field bitcoin.transactions | POST | data.bitcoin.transactions | Query Bitcoin transaction data. |
| ethereum_transactions | (GraphQL POST) root field ethereum.transactions | POST | data.ethereum.transactions | Query Ethereum transaction data. |
| health | https://docs.bitquery.io/v1/ (web) | GET | Documentation and health endpoint information. |
How do I authenticate with the Bitquery API?
Include the token in each request header as Authorization: Bearer <ACCESS_TOKEN>. For the GraphQL IDE and some streaming endpoints an X-API-KEY header or token in the URL is also supported.
1. Get your credentials
- Sign in or create an account at https://account.bitquery.io/. 2) Open "API Access Tokens" (Get Your Access Token) or visit https://account.bitquery.io/user/api_v2/access_tokens. 3) Create a new access token; copy the token value (store securely).
2. Add them to .dlt/secrets.toml
[sources.bitquery_transaction_api_source] api_key = "your_bitquery_access_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 Bitquery 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 bitquery_transaction_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline bitquery_transaction_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset bitquery_transaction_api_data The duckdb destination used duckdb:/bitquery_transaction_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline bitquery_transaction_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 transactions and calls from the Bitquery 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 bitquery_transaction_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://graphql.bitquery.io/", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "transactions", "endpoint": {"path": "(GraphQL POST to root)", "data_selector": "data.EVM.Transactions"}}, {"name": "calls", "endpoint": {"path": "(GraphQL POST to root)", "data_selector": "data.EVM.Calls"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bitquery_transaction_api_pipeline", destination="duckdb", dataset_name="bitquery_transaction_api_data", ) load_info = pipeline.run(bitquery_transaction_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("bitquery_transaction_api_pipeline").dataset() sessions_df = data.transactions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM bitquery_transaction_api_data.transactions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("bitquery_transaction_api_pipeline").dataset() data.transactions.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 Bitquery 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 Bitquery?
Request dlt skills, commands, AGENT.md files, and AI-native context.