Data.gov Python API Docs | dltHub
Build a Data.gov-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
api.data.gov is an API management service that provides a central entry point for accessing datasets and federal agency APIs through standardized key-based authentication. The REST API base URL is https://api.gsa.gov/technology/datagov/v4/ and requests require an API key passed via header, query parameter, or basic auth.
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 Data.gov data in under 10 minutes.
What data can I load from Data.gov?
Here are some of the endpoints you can load from Data.gov:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| package_search | /api/3/action/package_search | GET | result.results | Search datasets with optional filters and pagination. |
| package_list | /api/3/action/package_list | GET | result | List names of all site datasets. |
| organization_list | /api/3/action/organization_list | GET | result | List names of all organizations. |
| group_list | /api/3/action/group_list | GET | result | List names of all groups. |
| tag_list | /api/3/action/tag_list | GET | result | List names of all tags. |
| resource_show | /api/3/action/resource_show | GET | result | Retrieve specific resource details by ID. |
| current_package_list_with_resources | /api/3/action/current_package_list_with_resources | GET | result | List recent datasets including resources. |
How do I authenticate with the Data.gov API?
Authentication is performed using an API key which can be passed via the 'X-Api-Key' HTTP header, as a query parameter named 'api_key', or as the username in HTTP Basic Authentication. Requesting agencies require these keys to manage rate limiting and usage.
1. Get your credentials
To obtain an API key for services managed by api.data.gov, navigate to the official sign-up page at https://api.data.gov/signup/. After providing the necessary registration details, you will receive a unique 40-character API key via email. Note that for initial exploration of many datasets, you may use the demonstration key 'DEMO_KEY' without registration, though this is restricted to lower rate limits and is not suitable for production use.
2. Add them to .dlt/secrets.toml
[sources.data_gov_source] data_gov_api_key = "your_40_character_api_key_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 Data.gov 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 data_gov_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline data_gov_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset data_gov_data The duckdb destination used duckdb:/data_gov.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 package_search and package_show from the Data.gov 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 data_gov_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.gsa.gov/technology/datagov/v4/", "auth": {"type": "api_key", "api_key": api_key, "name": "X-Api-Key"}, }, "resources": [ {"name": "package_search", "endpoint": {"path": "api/3/action/package_search", "data_selector": "result.results"}}, {"name": "package_list", "endpoint": {"path": "api/3/action/package_list", "data_selector": "result"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="data_gov_pipeline", destination="duckdb", dataset_name="data_gov_data", ) load_info = pipeline.run(data_gov_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("data_gov_pipeline").dataset() sessions_df = data.package_search.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM data_gov_data.package_search LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("data_gov_pipeline").dataset() data.package_search.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 Data.gov 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 Data.gov?
Request dlt skills, commands, AGENT.md files, and AI-native context.