Load API Gateway API data in Python using dltHub
Build a API Gateway API-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
AWS API Gateway is a managed service that enables developers to create, publish, maintain, monitor, and secure REST APIs at any scale. The REST API base URL is https://{api-id}.execute-api.{region}.amazonaws.com/{stage} and Supports multiple methods: IAM (SigV4), API keys, Lambda authorizers, or Amazon Cognito..
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 API Gateway API data in under 10 minutes.
What data can I load from API Gateway API?
Here are some of the endpoints you can load from API Gateway API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| resources | /restapis/{restapi_id}/resources | GET | item | Lists resources for a REST API. |
| rest_apis | /restapis | GET | item | Lists all REST APIs for an account. |
| deployments | /restapis/{restapi_id}/deployments | GET | item | Lists all deployments for a REST API. |
| authorizers | /restapis/{restapi_id}/authorizers | GET | item | Lists all authorizers for a REST API. |
| models | /restapis/{restapi_id}/models | GET | item | Lists all models for a REST API. |
How do I authenticate with the API Gateway API API?
API Gateway supports multiple authentication mechanisms, including AWS IAM (Signature V4), API keys passed in an 'X-API-Key' header, Lambda authorizers (custom), and Amazon Cognito user pools. When using IAM authentication, requests require standard AWS V4 signing headers including X-Amz-Date and Authorization.
1. Get your credentials
To obtain an API key for an AWS API Gateway REST API: 1. Sign in to the AWS Management Console and open the API Gateway console. 2. In the navigation pane, choose 'API keys'. 3. Select 'Create API key' or import an existing key. 4. Provide a name and choose to either 'Auto generate' the value or enter a 'Custom' value. 5. Save the key. 6. Ensure your API stage is associated with a usage plan that includes this API key. 7. In API settings, ensure the 'API key source' is configured to 'HEADER' if you intend to pass the key in the request header.
2. Add them to .dlt/secrets.toml
[sources.api_gateway_api_source] api_key = "your_api_key_value_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 API Gateway 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 api_gateway_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline api_gateway_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset api_gateway_api_data The duckdb destination used duckdb:/api_gateway_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 get-api-key and get-api-keys from the API Gateway 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 api_gateway_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{api-id}.execute-api.{region}.amazonaws.com/{stage}", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "resources", "endpoint": {"path": "restapis/{restapi_id}/resources", "data_selector": "item"}}, {"name": "rest_apis", "endpoint": {"path": "restapis", "data_selector": "item"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="api_gateway_api_pipeline", destination="duckdb", dataset_name="api_gateway_api_data", ) load_info = pipeline.run(api_gateway_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("api_gateway_api_pipeline").dataset() sessions_df = data.resources.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM api_gateway_api_data.resources LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("api_gateway_api_pipeline").dataset() data.resources.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 API Gateway API 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 API Gateway API?
Request dlt skills, commands, AGENT.md files, and AI-native context.