Snowflake Python API Docs | dltHub
Build a Snowflake-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Snowflake REST API (including the SQL API) allows developers to programmatically access and interact with Snowflake data and resources. The REST API base URL is https://<account_identifier>.snowflakecomputing.com and all requests require a Bearer token 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 add "dlt[hub]" and start loading Snowflake data in under 10 minutes.
What data can I load from Snowflake?
Here are some of the endpoints you can load from Snowflake:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| databases | /api/v2/databases | GET | Lists accessible databases | |
| schemas | /api/v2/databases/{database}/schemas | GET | Lists schemas for a database | |
| tables | /api/v2/databases/{database}/schemas/{schema}/tables | GET | Lists tables for a schema | |
| warehouses | /api/v2/warehouses | GET | Lists warehouses | |
| users | /api/v2/users | GET | Lists users |
How do I authenticate with the Snowflake API?
All requests require an 'Authorization' header set to 'Bearer '. Additionally, an optional 'X-Snowflake-Authorization-Token-Type' header may be included (values: KEYPAIR_JWT, OAUTH, PROGRAMMATIC_ACCESS_TOKEN, WORKLOAD_IDENTITY_FEDERATION).
1. Get your credentials
Snowflake does not provide a single static 'API key' through a dashboard in the traditional sense for all REST operations. Instead, it uses secure authentication methods. For most integrations, a Programmatic Access Token (PAT) is the recommended approach. To obtain one: 1. Log in to your Snowflake account. 2. Navigate to your user settings or use the SQL command 'ALTER USER SET ENABLE_PROGRAMMATIC_ACCESS_TOKEN = TRUE;'. 3. Generate the token via the Snowflake console or SQL. Alternatively, you can use Key Pair authentication by generating a public-private key pair (using OpenSSL), assigning the public key to your Snowflake user via SQL ('ALTER USER SET RSA_PUBLIC_KEY = ...'), and then signing JWTs with your private key in your code.
2. Add them to .dlt/secrets.toml
[sources.snowflake_source] api_key = "REPLACE_ME"
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:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 Snowflake 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:
uv run python snowflake_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline snowflake_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset snowflake_data The duckdb destination used duckdb:/snowflake.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 '/api/v2/statements/ and /api/v2/statements/{statementHandle}' from the Snowflake API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def snowflake_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<account_identifier>.snowflakecomputing.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "databases", "endpoint": {"path": "api/v2/databases"}}, {"name": "tables", "endpoint": {"path": "api/v2/databases/{database}/schemas/{schema}/tables"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="snowflake_pipeline", destination="duckdb", dataset_name="snowflake_data", ) load_info = pipeline.run(snowflake_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):
import dlt data = dlt.pipeline("snowflake_pipeline").dataset() sessions_df = data.statements.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM snowflake_data.statements LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("snowflake_pipeline").dataset() data.statements.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 Snowflake data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Snowflake?
Request dlt skills, commands, AGENT.md files, and AI-native context.