Stripe - Crypto Onramp Quotes Python API Docs | dltHub

Stripe Crypto Onramp Quotes is an API that returns estimated fiat‑to‑crypto conversion quotes across supported cryptocurrencies and networks. The REST API base URL is https://api.stripe.com/v1 and all requests require HTTP Basic auth using your Stripe secret key (treated like a Bearer credential).

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 - Crypto Onramp Quotes data in under 10 minutes.

---

What data can I load from Stripe - Crypto Onramp Quotes?

Here are some of the endpoints you can load from Stripe - Crypto Onramp Quotes:

---

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

Use your Stripe secret key as the username in HTTP Basic auth (the password is blank). Alternatively send an Authorization header: Authorization: Bearer <SECRET_KEY>. For cURL examples Stripe shows -u "<SECRET_KEY>:" or Authorization: Bearer <SECRET_KEY>.

1. Get your credentials

1. Sign in to the Stripe Dashboard (https://dashboard.stripe.com). 2) Go to Developers > API keys. 3) Copy a secret key (starts with sk_test_ or sk_live_). 4) Use that secret key in requests as HTTP Basic username or Bearer token. 5) Keep secret keys private and use restricted keys in production as appropriate.

2. Add them to .dlt/secrets.toml

Copy
[sources.stripe_crypto_onramp_quotes_source]
api_key = "sk_test_XXXXXXXXXXXXXXXXXXXX"

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 - Crypto Onramp Quotes 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_crypto_onramp_quotes_pipeline.py

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

Copy
Pipeline stripe_crypto_onramp_quotes_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset stripe_crypto_onramp_quotes_data
The duckdb destination used duckdb:/stripe_crypto_onramp_quotes.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_crypto_onramp_quotes_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 crypto_onramp_quotes and crypto_onramp_quote_retrieve from the Stripe - Crypto Onramp Quotes 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_crypto_onramp_quotes_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.stripe.com/v1",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "crypto_onramp_quotes", "endpoint": {"path": "crypto/onramp/quotes", "data_selector": "destination_network_quotes"}},
            {"name": "crypto_onramp_quote_retrieve", "endpoint": {"path": "crypto/onramp/quotes", "data_selector": "destination_network_quotes"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="stripe_crypto_onramp_quotes_pipeline",
        destination="duckdb",
        dataset_name="stripe_crypto_onramp_quotes_data",
    )
    load_info = pipeline.run(stripe_crypto_onramp_quotes_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_crypto_onramp_quotes_pipeline").dataset()
sessions_df = data.crypto_onramp_quotes.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM stripe_crypto_onramp_quotes_data.crypto_onramp_quotes LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("stripe_crypto_onramp_quotes_pipeline").dataset()
data.crypto_onramp_quotes.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 - Crypto Onramp Quotes 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, verify you are using a valid Stripe secret key (sk_test_ or sk_live_) and that it is sent as HTTP Basic username or as Bearer token in the Authorization header. Ensure there are no extra characters or whitespace.

Rate limits

Stripe responds with 429 Too Many Requests when rate limits are hit. Retry with exponential backoff and inspect Retry-After header where provided.

Invalid request / parameter errors

Requests with invalid parameters return 4xx errors containing an error object with type, message, param. Ensure only one of source_amount or destination_amount is provided; when using destination_amount you must provide a single destination_currency and single destination_network.

Pagination and response shape

The Crypto Onramp Quotes endpoint returns a single CryptoOnrampQuotes object (not a paginated list). The list-like data you likely want is nested under the top-level key destination_network_quotes, which maps network names to arrays of quote entries.

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