MoonPay Python API Docs | dltHub
Build a MoonPay-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
MoonPay's API retrieves successful Buy transactions based on query parameters. The endpoint is at https://dev.moonpay.com/v1.0/reference/get_v1-transactions. Each transaction is returned as a separate entry in an array. The REST API base URL is https://api.moonpay.com and Requests require a publishable API key plus a cryptographic signature: RSA-SHA256 via x-signature for partner endpoints; HMAC-SHA256 signature (signature query param) for widget URL integrations..
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 MoonPay data in under 10 minutes.
What data can I load from MoonPay?
Here are some of the endpoints you can load from MoonPay:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| transactions | /v1/transactions | GET | transactions | Retrieve transactions (partner/general transactions listing). |
| virtual_accounts | /v1/virtual-accounts | GET | (top-level array) | List virtual accounts (example returns an array of account objects). |
| virtual_accounts_onramp_transactions | /v1/virtual-accounts/transactions/onramp | GET | transactions | Get on-ramp transactions for a virtual account (returns nextCursor + transactions array). |
| currencies | /v1/currencies | GET | (depends; often array) | List supported currencies and metadata. |
| public_keys | /v1/public-keys | GET | (depends) | Retrieve registered public keys / key metadata (for partners). |
| transactions_by_id | /v1/transactions/{id} | GET | (single object) | Retrieve a single transaction by id. |
| widget_url_sign | /v1/widget/signature (or client-side signing guidance) | POST/GET (integration) | - | Endpoint/process for generating widget signatures (docs show HMAC-SHA256 usage). |
How do I authenticate with the MoonPay API?
MoonPay partner APIs require request signing using RSA-SHA256 signatures in the x-signature header, along with the publishable API key (apiKey) and timestamp as query parameters. Widget/URL integrations use HMAC-SHA256 signatures generated with a secret key and appended as a signature query parameter.
1. Get your credentials
- Sign in to https://dashboard.moonpay.com/ 2) Navigate to the Developers tab on the sidebar -> API Keys. 3) Copy your publishable keys (pk_test_.../pk_live_...) and secret key (sk_test_/sk_live_). 4) For partner endpoints, register/upload a public key (RSA) in the Developers/Keys or Partner section and keep the matching private key locally for RSA-SHA256 signing.
2. Add them to .dlt/secrets.toml
[sources.moonpay_source] api_key = "pk_test_xxx" private_key = "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----" secret_key = "sk_test_xxx"
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 MoonPay 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 moonpay_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline moonpay_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset moonpay_data The duckdb destination used duckdb:/moonpay.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline moonpay_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 virtual_accounts from the MoonPay 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 moonpay_source(api_key (and private_key for RSA signing / secret_key for HMAC where required)=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.moonpay.com", "auth": { "type": "api_key", "api_key": api_key (and private_key for RSA signing / secret_key for HMAC where required), }, }, "resources": [ {"name": "transactions", "endpoint": {"path": "v1/transactions", "data_selector": "transactions"}}, {"name": "virtual_accounts", "endpoint": {"path": "v1/virtual-accounts"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="moonpay_pipeline", destination="duckdb", dataset_name="moonpay_data", ) load_info = pipeline.run(moonpay_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("moonpay_pipeline").dataset() sessions_df = data.transactions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM moonpay_data.transactions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("moonpay_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 MoonPay 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 MoonPay?
Request dlt skills, commands, AGENT.md files, and AI-native context.