Load Supabase data in Python using dltHub
Build a Supabase-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Supabase provides a RESTful data API powered by PostgREST that enables direct interaction with your PostgreSQL database tables and functions. The REST API base URL is https://<project_ref>.supabase.co/rest/v1 and requests require an 'apikey' header for the project key and an optional 'Authorization' header for user-specific JWTs.
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 Supabase data in under 10 minutes.
What data can I load from Supabase?
Here are some of the endpoints you can load from Supabase:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| table_rows | /{table} | GET | Select rows from a table (supports filtering, sorting, pagination, and column selection) | |
| table_rows_count | /{table} | GET | Get row count (using Prefer: count=exact header) | |
| rpc_function | /rpc/{function_name} | POST | Call a Postgres function | |
| table_rows_limited | /{table}?limit={n} | GET | Retrieve a limited number of rows | |
| table_rows_offset | /{table}?limit={n}&offset={m} | GET | Retrieve a limited number of rows with offset |
How do I authenticate with the Supabase API?
All requests require the 'apikey' header, which should be set to your project's publishable or secret API key. For authenticated requests, the 'Authorization' header must also be provided with a 'Bearer ' format, where the token is a user JWT or an access token.
1. Get your credentials
- Log in to your Supabase Dashboard. 2. Select your project from the dashboard. 3. In the sidebar, navigate to Settings > API Keys to find your API URL and keys (publishable and secret). Alternatively, you can use the Connect dialog accessible from the project overview page to quickly copy these credentials. Note that legacy keys (anon/service_role) may still be visible in the Legacy API Keys tab, but you should prioritize using the newer publishable and secret keys.
2. Add them to .dlt/secrets.toml
[sources.supabase_source] supabase_url = "https://<project_ref>.supabase.co" supabase_key = "<your_publishable_or_secret_key>"
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 Supabase 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 supabase_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline supabase_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset supabase_data The duckdb destination used duckdb:/supabase.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 /rest/v1/<table_name> and /rest/v1/rpc/<function_name> from the Supabase 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 supabase_source(apikey=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<project_ref>.supabase.co/rest/v1", "auth": {"type": "bearer", "token": apikey}, }, "resources": [ {"name": "table_rows", "endpoint": {"path": "{table}"}}, {"name": "table_rows_limited", "endpoint": {"path": "{table}?limit={limit}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="supabase_pipeline", destination="duckdb", dataset_name="supabase_data", ) load_info = pipeline.run(supabase_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("supabase_pipeline").dataset() sessions_df = data.table_rows.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM supabase_data.table_rows LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("supabase_pipeline").dataset() data.table_rows.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 Supabase 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 Supabase?
Request dlt skills, commands, AGENT.md files, and AI-native context.