Privy Python API Docs | dltHub
Build a Privy-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Privy is a developer API that provides wallet, user, authorization key, policy, and webhook management for blockchain applications. The REST API base URL is https://api.privy.io and All requests require Basic Auth and a Privy App ID 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 Privy data in under 10 minutes.
What data can I load from Privy?
Here are some of the endpoints you can load from Privy:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| wallets | v1/wallets | GET | List wallets (array of wallet objects) | |
| users | v1/users | GET | List users (array of user objects) | |
| transactions | v1/transactions | GET | List transactions (array of transaction objects) | |
| webhooks | v1/webhooks | GET | List webhooks (array of webhook objects) | |
| policies | v1/policies | GET | List policies (array of policy objects) |
How do I authenticate with the Privy API?
Privy uses HTTP Basic authentication where the Authorization header contains Base64(app_id:app_secret). Additionally include the privy-app-id header with your App ID and set Content-Type: application/json.
1. Get your credentials
- Sign in to the Privy Dashboard. 2) Create or select an App in the dashboard. 3) Locate the App ID and App Secret (app_secret) in the App's settings or API credentials section. 4) Use the App ID and App Secret to construct Basic auth (Base64 of "app_id:app_secret") and include the privy-app-id header.
2. Add them to .dlt/secrets.toml
[sources.privy_source] app_id = "your_app_id_here" app_secret = "your_app_secret_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 Privy 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 privy_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline privy_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset privy_data The duckdb destination used duckdb:/privy.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline privy_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 wallets and users from the Privy 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 privy_source(app_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.privy.io", "auth": { "type": "http_basic", "app_secret": app_secret, }, }, "resources": [ {"name": "wallets", "endpoint": {"path": "v1/wallets"}}, {"name": "users", "endpoint": {"path": "v1/users"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="privy_pipeline", destination="duckdb", dataset_name="privy_data", ) load_info = pipeline.run(privy_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("privy_pipeline").dataset() sessions_df = data.wallets.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM privy_data.wallets LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("privy_pipeline").dataset() data.wallets.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 Privy 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.
Troubleshooting
Authentication failures
Privy will return 401 Unauthorized for missing or invalid Authorization header or missing privy-app-id header. Ensure Authorization is Basic base64("app_id:app_secret") and include privy-app-id.
Rate limits
Privy returns 429 Too Many Requests when rate limits are exceeded. Implement exponential backoff retries.
Pagination and list responses
List endpoints return arrays of resource objects (no wrapper key). Use standard limit/offset or cursor query parameters if exposed by specific endpoint; otherwise paginate by API‑provided parameters.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Privy?
Request dlt skills, commands, AGENT.md files, and AI-native context.