Load Runpod S3 API data in Python using dltHub

Build a Runpod S3 API-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Runpod S3 API is an S3-compatible interface for managing files and datasets on Runpod network volumes. The REST API base URL is https://s3api-<datacenter>.runpod.io/ and all requests require AWS S3-compatible signature authentication using an Access Key ID and Secret Access Key.

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 Runpod S3 API data in under 10 minutes.


What data can I load from Runpod S3 API?

Here are some of the endpoints you can load from Runpod S3 API:

ResourceEndpointMethodData selectorDescription
pods/v2/podsGETList all active GPU pods
endpoints/v2/endpointsGETList all serverless endpoints
gpus/v2/gpusGETList available GPU types
user/v2/userGETGet user account info
templates/v2/templatesGETList available container templates

How do I authenticate with the Runpod S3 API API?

Authentication requires an S3 Access Key (your Runpod user ID) and a Secret Access Key. These credentials are used via standard AWS S3-compatible signature headers, not a Bearer token.

1. Get your credentials

To obtain S3-compatible API credentials, navigate to the Runpod console Settings page (https://www.console.runpod.io/user/settings). Expand the S3 API Keys section, select Create an S3 API key, and provide a name. Copy the access key (starts with user_) and the secret access key (starts with rps_). The secret is only displayed once; ensure it is saved securely. For general REST API access, navigate to the same Settings page, expand the API Keys section, and select Create API Key to generate a token for Bearer authentication.

2. Add them to .dlt/secrets.toml

[sources.runpod_s3_api_source] runpod_s3_access_key = "user_your_user_id_here" runpod_api_key = "your_bearer_token_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:

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 Runpod S3 API 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 runpod_s3_api_pipeline.py

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

Pipeline runpod_s3_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset runpod_s3_api_data The duckdb destination used duckdb:/runpod_s3_api.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 pods and endpoints from the Runpod S3 API 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 runpod_s3_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://s3api-<datacenter>.runpod.io/", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "pods", "endpoint": {"path": "/v2/pods"}}, {"name": "endpoints", "endpoint": {"path": "/v2/endpoints"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="runpod_s3_api_pipeline", destination="duckdb", dataset_name="runpod_s3_api_data", ) load_info = pipeline.run(runpod_s3_api_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("runpod_s3_api_pipeline").dataset() sessions_df = data.endpoints.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM runpod_s3_api_data.endpoints LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("runpod_s3_api_pipeline").dataset() data.endpoints.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 Runpod S3 API data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Runpod S3 API?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines