Stripe - Climate Python API Docs | dltHub

Stripe Climate is a Stripe service that enables merchants to purchase carbon removal and climate-related products (orders) and manage associated Climate resources. The REST API base URL is https://api.stripe.com/v1 and all requests require a Bearer (secret key) for authentication.

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 Stripe - Climate data in under 10 minutes.

---

What data can I load from Stripe - Climate?

Here are some of the endpoints you can load from Stripe - Climate:

---

How do I authenticate with the Stripe - Climate API?

Stripe uses API secret keys placed in the HTTP Basic auth username (or Authorization: Bearer <secret_key>) header. For REST API calls to https://api.stripe.com/v1, include your secret key as the username in basic auth or pass Authorization: Bearer sk_live_.../sk_test_... in the Authorization header.

1. Get your credentials

1. Sign in to your Stripe Dashboard at https://dashboard.stripe.com/. 2) Go to Developers -> API keys. 3) Create or copy a Standard secret key (sk_test_... or sk_live_...). 4) Use the secret key in requests as the Bearer token or in basic auth username.

2. Add them to .dlt/secrets.toml

Copy
[sources.stripe_climate_source]
api_key = "sk_test_your_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Stripe - Climate 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:

Copy
python stripe_climate_pipeline.py

If everything is configured correctly, you'll see output like this:

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

Inspect your pipeline and data:

Copy
dlt pipeline stripe_climate_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 orders and order from the Stripe - Climate API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def stripe_climate_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.stripe.com/v1",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "orders", "endpoint": {"path": "climate/orders", "data_selector": "data"}},
            {"name": "order", "endpoint": {"path": "climate/orders/{order_id}"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="stripe_climate_pipeline",
        destination="duckdb",
        dataset_name="stripe_climate_data",
    )
    load_info = pipeline.run(stripe_climate_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):

Copy
import dlt

data = dlt.pipeline("stripe_climate_pipeline").dataset()
sessions_df = data.orders.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM stripe_climate_data.orders LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("stripe_climate_pipeline").dataset()
data.orders.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 Stripe - Climate data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

If you receive a 401 Unauthorized, verify that you are sending a live or test secret key and that it is in the Authorization: Bearer <SECRET_KEY> header (or basic auth username). Use the correct mode (test keys for test mode).

Rate limits

Stripe returns 429 Too Many Requests when rate limits are hit. Inspect Retry-After header and back off; implement exponential backoff.

Pagination

List endpoints (e.g., GET /v1/climate/orders) are paginated and return a top-level data array plus has_more and next/starting_after style pagination tokens. Use provided pagination parameters (limit, starting_after).

Common errors

400 Bad Request — invalid parameters; 401 Unauthorized — invalid/missing credentials; 402 Payment Required — payment-related failures; 404 Not Found — invalid resource ID; 429 Too Many Requests — rate limiting.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack