Phantom Python API Docs | dltHub

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

Last updated:

Phantom's API allows connecting to user accounts and signing messages. The provider is accessible via window.phantom. Direct integration uses the provider for Bitcoin interactions. The REST API base URL is Not applicable. Phantom does not expose a traditional REST HTTP API; it uses a browser-injected provider object. and Authorization is handled by the user approving interactions within their Phantom extension or mobile app; there are no API tokens or HTTP authentication..

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 Phantom data in under 10 minutes.


What data can I load from Phantom?

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

Not applicable. Phantom does not expose a REST HTTP API with traditional GET endpoints. Interactions are via methods on a browser-injected provider object (e.g., window.phantom.ethereum or window.phantom.bitcoin). These methods include requestAccounts, signMessage, signPSBT, signTransaction, signAndSendTransaction, and sendTransaction. They return values via JavaScript promises, not JSON REST responses, and thus do not have data selectors.

How do I authenticate with the Phantom API?

Authorization is managed by the user approving requests within their Phantom wallet interface. Dapps interact with an injected provider object to request actions, which the user then authorizes.

1. Get your credentials

Phantom does not use traditional API credentials. To integrate, a dapp must detect the injected phantom object (e.g., window.phantom.bitcoin or window.phantom.ethereum) in the browser. Then, call provider methods like requestAccounts to prompt the user to connect and authorize actions through their Phantom wallet interface.

2. Add them to .dlt/secrets.toml

[sources.phantom_provider_api_source] Not applicable (no API keys or server-side credentials).

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 Phantom 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 phantom_provider_api_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline phantom_provider_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 Not applicable (no REST endpoints). from the Phantom 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 phantom_provider_api_source(Not applicable (no server-side credentials for a dlt source).=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "Not applicable. Phantom does not expose a traditional REST HTTP API; it uses a browser-injected provider object.", "auth": { "type": "none", "Not applicable (no API tokens).": Not applicable (no server-side credentials for a dlt source)., }, }, "resources": [ ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="phantom_provider_api_pipeline", destination="duckdb", dataset_name="phantom_provider_api_data", ) load_info = pipeline.run(phantom_provider_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("phantom_provider_api_pipeline").dataset() sessions_df = data.Not applicable (no REST endpoints)..df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM phantom_provider_api_data.Not applicable (no REST endpoints). LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("phantom_provider_api_pipeline").dataset() data.Not applicable (no REST endpoints)..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 Phantom 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 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 Phantom?

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