ProPublica Congress API Python API Docs | dltHub
Build a ProPublica Congress API-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
The ProPublica Congress API provided programmatic access to legislative data from the U.S. House, Senate, and Library of Congress. The REST API base URL is https://api.propublica.org/congress/v1 and all requests require an X-API-Key header containing the API 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 ProPublica Congress API data in under 10 minutes.
What data can I load from ProPublica Congress API?
Here are some of the endpoints you can load from ProPublica Congress API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| votes_recent | {chamber}/votes/recent.json | GET | results | Returns the 20 most recent votes |
| bill_search | bills/search.json?query={query} | GET | results | Search bills by keyword |
| committee_hearings | {congress}/committees/hearings.json | GET | results | List of 20 upcoming committee hearings |
| lobbying_search | lobbying/search.json?query={query} | GET | results | Search lobbying representation filings |
| bill_cosponsors | {congress}/bills/{bill-id}/cosponsors.json | GET | results | Get cosponsors for a specific bill |
How do I authenticate with the ProPublica Congress API API?
Authentication is performed by passing the API key as a custom request header named X-API-Key.
1. Get your credentials
The ProPublica Congress API is no longer available and is currently maintained only as a historical reference. ProPublica officially states that new API keys are no longer being issued or supported. Consequently, there is no active dashboard or registration process for obtaining credentials.
2. Add them to .dlt/secrets.toml
[sources.propublica_congress_api_source] # Note: This API is deprecated and no longer functional. # X-API-Key is the header used in historical implementations. x_api_key = "your_deprecated_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 ProPublica Congress 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 propublica_congress_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline propublica_congress_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset propublica_congress_api_data The duckdb destination used duckdb:/propublica_congress_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 votes/recent and members from the ProPublica Congress 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 propublica_congress_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.propublica.org/congress/v1", "auth": {"type": "api_key", "api_key": api_key, "name": "X-API-Key", "location": "header"}, }, "resources": [ {"name": "votes_recent", "endpoint": {"path": "house/votes/recent.json", "data_selector": "results"}}, {"name": "bill_search", "endpoint": {"path": "bills/search.json", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="propublica_congress_api_pipeline", destination="duckdb", dataset_name="propublica_congress_api_data", ) load_info = pipeline.run(propublica_congress_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("propublica_congress_api_pipeline").dataset() sessions_df = data.votes_recent.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM propublica_congress_api_data.votes_recent LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("propublica_congress_api_pipeline").dataset() data.votes_recent.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 ProPublica Congress 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 ProPublica Congress API?
Request dlt skills, commands, AGENT.md files, and AI-native context.