CryptoProcessing Python API Docs | dltHub
Build a CryptoProcessing-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
CryptoProcessing is a payment processing platform API for managing balances, currencies, deposits, withdrawals, and payments. The REST API base URL is https://app.cryptoprocessing.com/api/v2 and all requests require custom HMAC-SHA512 signature headers with an API key.
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 CryptoProcessing data in under 10 minutes.
What data can I load from CryptoProcessing?
Here are some of the endpoints you can load from CryptoProcessing:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| balances | accounts/list | POST | data | Get a list of account balances |
| currencies | currencies | GET | List supported currencies | |
| deposit_addresses | deposit-addresses | GET | List deposit addresses | |
| invoices | stores//invoices | GET | List invoices for a store | |
| transactions | transactions | GET | List transactions |
How do I authenticate with the CryptoProcessing API?
Requests must include Content-Type: application/json, X-Processing-Key (your API key), and X-Processing-Signature (an HMAC-SHA512 hex-encoded signature of the raw request body). The signature is created using your secret key as the HMAC key and the exact, non-formatted JSON request body string.
1. Get your credentials
- Log in to your CryptoProcessing merchant dashboard. 2. Navigate to the API keys tab (often located under API settings). 3. Click the Generate API key button. 4. After the key appears, click the Activate button next to it. 5. Enter your 2FA code when prompted. 6. The secret key will be displayed immediately; ensure you copy and save it securely, as it will not be visible again.
2. Add them to .dlt/secrets.toml
[sources.cryptoprocessing_source] api_key = "your_x_processing_key_here" secret_key = "your_hmac_secret_key_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 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 CryptoProcessing 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 cryptoprocessing_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline cryptoprocessing_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cryptoprocessing_data The duckdb destination used duckdb:/cryptoprocessing.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 v2/accounts/list and v2/addresses/take from the CryptoProcessing 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 cryptoprocessing_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://app.cryptoprocessing.com/api/v2", "auth": {"type": "api_key", "api_key": api_key, "name": "Authorization", "location": "header"}, }, "resources": [ {"name": "balances", "endpoint": {"path": "accounts/list", "data_selector": "data"}}, {"name": "currencies", "endpoint": {"path": "currencies"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cryptoprocessing_pipeline", destination="duckdb", dataset_name="cryptoprocessing_data", ) load_info = pipeline.run(cryptoprocessing_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("cryptoprocessing_pipeline").dataset() sessions_df = data.invoices.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM cryptoprocessing_data.invoices LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("cryptoprocessing_pipeline").dataset() data.invoices.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 CryptoProcessing 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 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 CryptoProcessing?
Request dlt skills, commands, AGENT.md files, and AI-native context.