Fireblocks Python API Docs | dltHub

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

Last updated:

Fireblocks provides a robust REST API for managing digital assets, accounts, and transactions programmatically. The REST API base URL is https://api.fireblocks.io/v1 and all requests require an API key and a signed JWT Bearer token in the 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 add "dlt[hub]" and start loading Fireblocks data in under 10 minutes.


What data can I load from Fireblocks?

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

ResourceEndpointMethodData selectorDescription
vault_accountsv1/vault/accounts_pagedGETaccountsRetrieves a paginated list of vault accounts.
assetsv1/supported_assetsGETRetrieves a paginated list of all supported assets.
audit_logsv1/management/audit_logsGETRetrieves audit log events for the workspace.
legal_entitiesv1/legal_entitiesGETReturns legal entity registrations.
address_registry_vaultsv1/address_registry/vaultsGETLists vault accounts opted out of the address registry.

How do I authenticate with the Fireblocks API?

All requests must be authenticated using an API key and a request-signing process. The request requires two headers: 'X-API-Key' (your API User ID) and 'Authorization' set to 'Bearer ', where the JWT is a Base64-encoded token signed with your RSA private key.

1. Get your credentials

  1. Generate an RSA 4096 private key and a Certificate Signing Request (CSR) file using OpenSSL: 'openssl req -new -newkey rsa
    -nodes -keyout fireblocks_secret.key -out fireblocks.csr -subj '/O=<your_organization>''. 2. Log in to the Fireblocks Console and navigate to the Developer Center > API Users page. 3. Click 'Add API user', provide a display name, and select the appropriate role. 4. Upload the 'fireblocks.csr' file generated in step 1. 5. Once the request is approved (if applicable), the API User (ID) will appear in the API users list. Copy this ID; it serves as your API key. Keep the 'fireblocks_secret.key' file secure, as it is required to sign all API requests.

2. Add them to .dlt/secrets.toml

[sources.fireblocks_source] fireblocks_api_key = "your_api_user_id_here" fireblocks_secret_key_path = "/path/to/your/fireblocks_secret.key"

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 Fireblocks 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 fireblocks_pipeline.py

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

Pipeline fireblocks_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fireblocks_data The duckdb destination used duckdb:/fireblocks.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 vault/accounts and transactions from the Fireblocks 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 fireblocks_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.fireblocks.io/v1", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "vault_accounts", "endpoint": {"path": "v1/vault/accounts_paged", "data_selector": "accounts"}}, {"name": "assets", "endpoint": {"path": "v1/supported_assets"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fireblocks_pipeline", destination="duckdb", dataset_name="fireblocks_data", ) load_info = pipeline.run(fireblocks_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("fireblocks_pipeline").dataset() sessions_df = data.vault_accounts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM fireblocks_data.vault_accounts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("fireblocks_pipeline").dataset() data.vault_accounts.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 Fireblocks 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 Fireblocks?

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

Available Pipelines