Regulations.gov Python API Docs | dltHub

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

Last updated:

Regulations.gov is a federal government portal providing programmatic access to regulatory dockets, documents, and public comments. The REST API base URL is https://api.regulations.gov and all requests require an API key sent in the X-Api-Key header.

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 Regulations.gov data in under 10 minutes.


What data can I load from Regulations.gov?

Here are some of the endpoints you can load from Regulations.gov:

ResourceEndpointMethodData selectorDescription
documents/v4/documentsGETdataSearch and list documents
document/v4/documents/{documentId}GETGet details of a single document
comments/v4/commentsGETdataSearch and list comments
comment/v4/comments/{commentId}GETGet details of a single comment
dockets/v4/docketsGETdataSearch and list dockets
docket/v4/dockets/{docketId}GETGet details of a single docket

How do I authenticate with the Regulations.gov API?

Requests require an API key to be passed in the X-Api-Key HTTP header. A DEMO_KEY is available for testing purposes, but production use requires registering for a unique key via api.data.gov.

1. Get your credentials

To obtain API credentials for the Regulations.gov REST API, visit the official GSA API portal at https://open.gsa.gov/api/regulationsgov/ and follow the registration link (provided via api.data.gov) to sign up for an API key. Once registered, you will receive a unique 40-character API key string which must be included in the 'X-Api-Key' HTTP header of your requests. For demonstration purposes only, the API accepts the string 'DEMO_KEY'.

2. Add them to .dlt/secrets.toml

[sources.regulations_gov_source] api_key = "YOUR_REGS_GOV_API_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 Regulations.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 regulations_gov_pipeline.py

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

Pipeline regulations_gov_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset regulations_gov_data The duckdb destination used duckdb:/regulations_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 /v4/documents and /v4/comments from the Regulations.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 regulations_gov_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.regulations.gov", "auth": {"type": "api_key", "api_key": api_key, "name": "X-Api-Key", "location": "header"}, }, "resources": [ {"name": "documents", "endpoint": {"path": "v4/documents", "data_selector": "data"}}, {"name": "comments", "endpoint": {"path": "v4/comments", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="regulations_gov_pipeline", destination="duckdb", dataset_name="regulations_gov_data", ) load_info = pipeline.run(regulations_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("regulations_gov_pipeline").dataset() sessions_df = data.documents.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM regulations_gov_data.documents LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("regulations_gov_pipeline").dataset() data.documents.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 Regulations.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 Regulations.gov?

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

Available Pipelines