Gsa Gov Python API Docs | dltHub

Build a Gsa Gov-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

GSA Open Technology provides various REST APIs for government data and services often managed via the api.data.gov platform. The REST API base URL is https://api.gsa.gov/ and all requests require an API key via X-Api-Key header or query parameter.

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 Gsa Gov data in under 10 minutes.


What data can I load from Gsa Gov?

Here are some of the endpoints you can load from Gsa Gov:

ResourceEndpointMethodData selectorDescription
opportunity_searchsam.gov/prod/opportunity/v3/searchGETopportunitiesSearch contract opportunities (paginated via limit/offset)
entity_searchentity-information/v4/entitiesGETresultsSearch entities (synchronous, paginated)
catalog_searchtechnology/datagov/v4/searchGETSearch data.gov catalog (paginated via cursor)
searchgov_resultssearchgov/api/v2/searchGETresultsSearch SearchGov results (paginated via offset)
extract_metadatadata-services/v1/extractsGETresultsRetrieve extract file metadata

How do I authenticate with the Gsa Gov API?

Most GSA-managed APIs use an API key provided by api.data.gov, typically passed in the 'X-Api-Key' HTTP header. Some endpoints may also support passing the key as a query parameter or using HTTP Basic Auth for specific system accounts.

1. Get your credentials

To obtain an API key for general GSA and Data.gov REST APIs, navigate to the official api.data.gov sign-up page (https://api.data.gov/signup) and complete the registration form to receive your unique key. For specialized SAM.gov APIs, log in to your account at https://sam.gov, navigate to your Workspace profile settings, and locate the 'Public API Key' section. For restricted system-level access, you must set up a 'System Account' via the 'System Accounts' widget in your SAM.gov Workspace, approve it, and generate a specific system API key by entering your system account password.

2. Add them to .dlt/secrets.toml

[sources.gsa_gov_source] api_key = "your_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 Gsa 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 gsa_gov_pipeline.py

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

Pipeline gsa_gov_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset gsa_gov_data The duckdb destination used duckdb:/gsa_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 search from the Gsa 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 gsa_gov_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.gsa.gov/", "auth": {"type": "api_key", "api_key": api_key, "name": "x-api-key", "location": "header"}, }, "resources": [ {"name": "catalog_search", "endpoint": {"path": "technology/datagov/v4/search"}}, {"name": "entity_search", "endpoint": {"path": "entity-information/v4/entities", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="gsa_gov_pipeline", destination="duckdb", dataset_name="gsa_gov_data", ) load_info = pipeline.run(gsa_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("gsa_gov_pipeline").dataset() sessions_df = data.entity_search.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM gsa_gov_data.entity_search LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("gsa_gov_pipeline").dataset() data.entity_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 Gsa Gov 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 Gsa Gov?

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