Load Recharge data in Python using dltHub

Build a Recharge-to-database or-dataframe pipeline in Python using dlt with automatic cursor support.

In this guide, we'll set up a complete Recharge data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source
def recharge_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.rechargeapps.com/v1/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            "checkouts",
            "customers",
            "charges"
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='recharge_pipeline',
        destination='duckdb',
        dataset_name='recharge_data', 
    )
    # Load the data
    load_info = pipeline.run(recharge_source())
    print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

  • Accelerate pipeline development with AI-native context
  • Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
  • Build Python notebooks for end users of your data
  • Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
  • dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from recharge’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Checkouts: Manage checkout processes and retrieve checkout information.
  • Customers: Access customer data, including their addresses and subscriptions.
  • Charges: Handle charge data related to orders and subscriptions, including refunds.
  • Addresses: Manage customer addresses and their associated information.
  • Discounts: Handle discount codes and their application to checkouts or addresses.

You will then debug the Recharge pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡
Before getting started, let's make sure Cursor is set up correctly:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install dlt[workspace]

    Initialize a dlt pipeline with Recharge support.

    dlt init dlthub:recharge duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for Recharge API, as specified in @recharge-docs.yaml 
Start with endpoints "checkouts" and "customers" and skip incremental loading for now. 
Place the code in recharge_pipeline.py and name the pipeline recharge_pipeline. 
If the file exists, use it as a starting point. 
Do not add or modify any other files. 
Use @dlt rest api as a tutorial. 
After adding the endpoints, allow the user to run the pipeline with python recharge_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    The Recharge API uses API key authentication, which requires the API key to be passed in the header as 'X-Recharge-Access-Token'. The API token must have the correct permissions for the endpoints being accessed.

    To get the appropriate API keys, please visit the original source at https://rechargepayments.com/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

  4. 🏃‍♀️ Run the pipeline in the Python terminal in Cursor

    python recharge_pipeline.py

    If your pipeline runs correctly, you’ll see something like the following:

    Pipeline recharge load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset recharge_data
The duckdb destination used duckdb:/recharge.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

  5. 📈 Debug your pipeline and data with the Pipeline Dashboard

    Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:

    • Pipeline overview: State, load metrics
    • Data’s schema: tables, columns, types, hints
    • You can query the data itself
    dlt pipeline recharge_pipeline show --dashboard

  6. 🐍 Build a Notebook with data explorations and reports

    With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.

    import dlt

data = dlt.pipeline("recharge_pipeline").dataset()
# get "checkouts" table as Pandas frame
data.checkouts.df().head()

Running into errors?

When using the Recharge API, it's important to note that charges processed over 90 days ago will not be retrievable through the API and will need to be accessed via the Exports tool in the Recharge merchant portal. Additionally, endpoint paths often require specific IDs to be replaced, and the API supports both cursor and page-based pagination, though cursor pagination is preferred for performance. Be aware of rate limits, particularly when making multiple requests in a short time frame.

Extra resources:

Next steps