Stripe - Payments Python API Docs | dltHub

Stripe is a payments platform that provides REST APIs to accept and manage online payments, payment methods, customers, and related payment objects. The REST API base URL is https://api.stripe.com and all requests require a Bearer token (secret API key) in the Authorization 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 pip install "dlt[workspace]" and start loading Stripe - Payments data in under 10 minutes.

---

What data can I load from Stripe - Payments?

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

---

How do I authenticate with the Stripe - Payments API?

Stripe authenticates requests using a secret API key sent in the Authorization header as a Bearer token (Authorization: Bearer <SECRET_KEY>). For some v2 endpoints you must also include the Stripe-Version header to target a particular API version.

1. Get your credentials

1. Sign in to the Stripe Dashboard (https://dashboard.stripe.com). 2. In Developers > API keys, copy your Secret key (starts with sk_live_ or sk_test_). 3. Use the test key for development; use the live key in production after account activation.

2. Add them to .dlt/secrets.toml

Copy
[sources.stripe_payments_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 - 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:

Copy
python stripe_payments_pipeline.py

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

Copy
Pipeline stripe_payments_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset stripe_payments_data
The duckdb destination used duckdb:/stripe_payments.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_payments_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 payment_intents and payment_methods from the Stripe - Payments 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_payments_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.stripe.com",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "payment_intents", "endpoint": {"path": "v1/payment_intents", "data_selector": "data"}},
            {"name": "payment_methods", "endpoint": {"path": "v1/payment_methods", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


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

Copy
import dlt

data = dlt.pipeline("stripe_payments_pipeline").dataset()
sessions_df = data.payment_intents.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM stripe_payments_data.payment_intents LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("stripe_payments_pipeline").dataset()
data.payment_intents.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 - Payments 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 401 Unauthorized or 'Invalid API Key' errors, verify you're using the secret key (starts with sk_test_ or sk_live_) in the Authorization header as: Authorization: Bearer <SECRET_KEY>. Ensure you are not using a publishable key (pk_...). Also confirm you are calling the correct environment (test vs live) and that the key has not been revoked.

Rate limits

Stripe returns 429 Too Many Requests when rate limits are exceeded. Retry after a backoff (exponential) and respect any Retry-After header. Use idempotency keys (Idempotency-Key) for POST/DELETE operations to safely retry.

Pagination

Most v1 list endpoints return an object with a 'data' array and pagination fields like 'has_more' and 'url'. Use the 'starting_after' and 'ending_before' query parameters to page through results. v2 endpoints use 'previous_page_url' and 'next_page_url'.

Common error responses

Stripe uses standard HTTP status codes. Common errors include 400 (invalid request parameters), 401 (authentication errors), 402 (card errors for payments), 403 (forbidden), 404 (not found), 429 (rate limit). Error response bodies contain an 'error' object with 'type', 'message', and 'code' fields.

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