Load Stripe - Crypto Onramp Sessions data to DuckDB

Stripe Crypto Onramp Sessions is an API service for managing and retrieving customer cryptocurrency purchase sessions. Everything needed to build a working Stripe - Crypto Onramp Sessions → 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 Stripe - Crypto Onramp Sessions 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 Stripe - Crypto Onramp Sessions 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 Stripe - Crypto Onramp Sessions 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.

---

Stripe - Crypto Onramp Sessions API at a glance

These values come from the Stripe - Crypto Onramp Sessions API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Stripe - Crypto Onramp Sessions API?

Stripe authenticates requests using HTTP Basic Auth, providing the API key as the username without a password. Alternatively, for cross-origin requests, you can use the Authorization: Bearer header.

1. Get your credentials

1. Navigate to the Stripe Dashboard at https://dashboard.stripe.com/apikeys. 2. Ensure you are in either 'Test mode' or 'Live mode' as required by your environment. 3. Click the 'Create secret key' button. 4. Provide a name for the key and click 'Create'. 5. Copy the secret key immediately, as it cannot be retrieved again. 6. Use this secret key for server-side API requests. For public-facing client-side SDK initializations, use the 'Publishable key' found on the same page.

2. Add them to .dlt/secrets.toml

Copy
[sources.stripe_crypto_onramp_sessions_source]
api_key = "sk_test_..."

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 Stripe - Crypto Onramp Sessions data can I load into DuckDB?

These are the Stripe - Crypto Onramp Sessions endpoints dlt can load into DuckDB:

---

How do I load only new Stripe - Crypto Onramp Sessions records?

Stripe - Crypto Onramp Sessions exposes starting_after on v1/crypto/onramp_sessions, 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": "crypto_onramp_sessions", "endpoint": {
    "path": "v1/crypto/onramp_sessions",
    "data_selector": "data",
    "incremental": {"cursor_path": "starting_after", "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 Stripe - Crypto Onramp Sessions pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v1/crypto/onramp_sessions and /v1/crypto/onramp_sessions/:id from the Stripe - Crypto Onramp Sessions API into DuckDB:

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

@dlt.source
def stripe_crypto_onramp_sessions_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.stripe.com",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key},
        },
        "resources": [
            {"name": "crypto_onramp_sessions", "endpoint": {"path": "v1/crypto/onramp_sessions", "data_selector": "data"}},
            {"name": "crypto_onramp_sessions_list", "endpoint": {"path": "v1/crypto/onramp_sessions", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_stripe_crypto_onramp_sessions_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="stripe_crypto_onramp_sessions_pipeline",
        destination="duckdb",
        dataset_name="stripe_crypto_onramp_sessions_data",
    )
    load_info = pipeline.run(stripe_crypto_onramp_sessions_source())
    print(load_info)


if __name__ == "__main__":
    load_stripe_crypto_onramp_sessions_to_duckdb()

Run it with python stripe_crypto_onramp_sessions_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 Stripe - Crypto Onramp Sessions 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("stripe_crypto_onramp_sessions_pipeline").dataset()
df = data.crypto_onramp_sessions.df()
print(df.head())

SQL:

Copy
SELECT * FROM stripe_crypto_onramp_sessions_data.crypto_onramp_sessions LIMIT 10;

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

---

How do I deploy the Stripe - Crypto Onramp Sessions 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 Stripe - Crypto Onramp Sessions 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 Stripe - Crypto Onramp Sessions 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