Load Recharge Payments data to DuckDB

Recharge Payments is a subscription management and recurring billing platform that provides a REST API for managing stores, subscriptions, and customers. Everything needed to build a working Recharge Payments → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Recharge Payments to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Recharge Payments to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Recharge Payments API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Recharge Payments API at a glance

These values come from the Recharge Payments API reference — the authoritative source if anything here looks out of date.

---

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

Copy
[sources.recharge_payments_source]
api_token = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Recharge Payments data can I load into DuckDB?

These are the Recharge Payments endpoints dlt can load into DuckDB:

---

How do I load only new Recharge Payments records?

Recharge Payments exposes updated_at on customers, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "customers", "endpoint": {
    "path": "customers",
    "data_selector": "customers",
    "incremental": {"cursor_path": "updated_at", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Recharge Payments pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /subscriptions and /customers from the Recharge Payments API into DuckDB:

Copy
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 load_recharge_payments_to_duckdb() -> 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)


if __name__ == "__main__":
    load_recharge_payments_to_duckdb()

Run it with python recharge_payments_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Recharge Payments data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("recharge_payments_pipeline").dataset()
df = data.subscriptions.df()
print(df.head())

SQL:

Copy
SELECT * FROM recharge_payments_data.subscriptions LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Recharge Payments to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Recharge Payments loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Recharge Payments data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack