Recharge Payments Python API Docs | dltHub
Build a Recharge Payments-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Recharge Payments is a subscription management and recurring billing platform that provides a REST API for managing stores, subscriptions, and customers. The REST API base URL is https://api.rechargeapps.com and all requests require an API key passed in a 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 add "dlt[hub]" and start loading Recharge Payments data in under 10 minutes.
What data can I load from Recharge Payments?
Here are some of the endpoints you can load from Recharge Payments:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| addresses | /addresses | GET | addresses | Returns a list of customer addresses |
| charges | /charges | GET | charges | Returns a list of charges |
| customers | /customers | GET | customers | Returns a list of customers |
| orders | /orders | GET | orders | Returns a list of orders |
| subscriptions | /subscriptions | GET | subscriptions | Returns a list of subscriptions |
How do I authenticate with the Recharge Payments API?
Authentication is performed by passing an API key in the custom header X-Recharge-Access-Token. All requests must be made over HTTPS.
1. Get your credentials
To obtain your Recharge API credentials: 1. Log in to the Recharge merchant portal. 2. Navigate to 'Tools & apps' in the sidebar. 3. Click on 'API tokens'. 4. Click 'Create an API Token'. 5. Enter a nickname and contact email for the token. 6. Select the appropriate permission scopes (e.g., Read or Read and Write) as required by your integration. 7. Click 'Save' to generate the token and copy it immediately for use in your application.
2. Add them to .dlt/secrets.toml
[sources.recharge_payments_source] api_token = "REPLACE_ME"
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 Recharge Payments 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 recharge_payments_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline recharge_payments_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset recharge_payments_data The duckdb destination used duckdb:/recharge_payments.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 /subscriptions and /customers from the Recharge Payments 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 recharge_payments_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.rechargeapps.com", "auth": {"type": "api_key", "api_key": api_token, "name": "X-Recharge-Access-Token", "location": "header"}, }, "resources": [ {"name": "customers", "endpoint": {"path": "customers", "data_selector": "customers"}}, {"name": "subscriptions", "endpoint": {"path": "subscriptions", "data_selector": "subscriptions"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="recharge_payments_pipeline", destination="duckdb", dataset_name="recharge_payments_data", ) load_info = pipeline.run(recharge_payments_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("recharge_payments_pipeline").dataset() sessions_df = data.subscriptions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM recharge_payments_data.subscriptions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("recharge_payments_pipeline").dataset() data.subscriptions.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 Recharge Payments 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 Recharge Payments?
Request dlt skills, commands, AGENT.md files, and AI-native context.