disclosures-clerk.house.gov APIdisclosures-clerk.house.gov ↗
Extract structured transaction data from Congressional PTR filings via 2 endpoints. Returns trades, tickers, amounts, and pie chart aggregations by asset or transaction type.
curl -X GET 'https://api.parse.bot/scraper/e5422bf1-5120-4283-b715-3992bedee252/get_transactions' \ -H 'X-API-Key: $PARSE_API_KEY'
Extract all transactions from a Congressional financial disclosure filing (PTR). Parses the PDF and returns structured data including asset name, ticker, transaction type, date, amount range, and description for each transaction.
| Param | Type | Description |
|---|---|---|
| year | string | Year the filing was made (used in PDF URL path). |
| filing_id | string | Filing ID number from the House disclosure system. |
{
"type": "object",
"fields": {
"filer": "object containing name, status, state_district, filing_id, signed",
"filing_id": "string, the filing ID",
"transactions": "array of transaction objects each with owner, asset, ticker, asset_type_code, transaction_type, transaction_type_code, date, notification_date, amount_range, amount_midpoint, description",
"transaction_count": "integer, number of transactions parsed"
},
"sample": {
"data": {
"filer": {
"name": "Hon. Nancy Pelosi",
"signed": "Hon. Nancy Pelosi , 01/23/2026",
"status": "Member",
"filing_id": "20033725",
"state_district": "CA11"
},
"filing_id": "20033725",
"transactions": [
{
"date": "01/16/2026",
"asset": "AllianceBernstein Holding L.P. Units",
"owner": "SP",
"ticker": null,
"description": "Purchased 25,000 shares.",
"amount_range": "$1,000,001 - $5,000,000",
"amount_midpoint": 3000000,
"asset_type_code": "AB",
"transaction_type": "Purchase",
"notification_date": "01/16/2026",
"transaction_type_code": "P"
}
],
"transaction_count": 18
},
"status": "success"
}
}About the disclosures-clerk.house.gov API
This API exposes 2 endpoints for extracting and aggregating financial transaction data from Congressional Periodic Transaction Reports (PTRs) filed with the House of Representatives. The get_transactions endpoint returns structured records for every trade in a filing — including asset name, ticker symbol, transaction type, date, and amount range — while get_pie_chart_data groups those transactions by asset or transaction type with midpoint-based dollar values and percentages.
What the API covers
The API reads from House PTR filings identified by a filing_id and optional year parameter. Each filing is tied to a specific member of Congress; the filer object in every response includes the member's name, status, state and district, filing ID, and signature date. The get_transactions endpoint returns a transactions array alongside a transaction_count integer, so you know immediately how many trades a given filing contains.
Transaction-level fields
Each transaction object in the transactions array includes: owner (who holds the asset), asset (full name), ticker (exchange symbol where available), asset_type_code, transaction_type (buy, sell, exchange, etc.), transaction_type_code, date, and notif (notification flag). These fields map directly to what filers report under the STOCK Act disclosure requirements.
Aggregation with get_pie_chart_data
The get_pie_chart_data endpoint accepts a group_by parameter with two accepted values: asset (groups by ticker) or transaction_type. It returns a slices array where each slice has a label, a value computed from midpoints of reported amount ranges, and a percentage of the total_value. This lets you quickly compare concentration across holdings or trade direction without post-processing the raw transaction list yourself.
Filing identification
Both endpoints require a filing_id from the House disclosure system. The year parameter is used to construct the correct path to the underlying filing. Filing IDs are publicly listed on disclosures-clerk.house.gov and can be discovered by browsing the PTR search interface on that site.
- Track all buy and sell transactions for a specific member of Congress by filing ID and year.
- Identify which ticker symbols appear most frequently across a congressional disclosure filing.
- Build a portfolio snapshot of reported holdings using asset name and transaction type fields.
- Generate pie chart breakdowns of trade activity by asset or transaction direction for a given PTR.
- Monitor notification flags (
notif) to surface late-reported transactions under STOCK Act rules. - Compare total reported transaction value across multiple filings using
total_valuefrom aggregation responses. - Cross-reference congressional trades with market dates using the
datefield on each transaction.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does disclosures-clerk.house.gov have an official developer API?+
What does get_transactions return for a filing, and how detailed are the amount fields?+
transactions array where each entry includes owner, asset name, ticker, asset type code, transaction type, transaction type code, date, and a notification flag. Amount ranges are reported as ranges (e.g. $1,001–$15,000) matching what filers disclose — the raw transaction records do not resolve to a single dollar figure. The get_pie_chart_data endpoint uses midpoints of those ranges to produce numeric value and percentage fields per slice.Does the API cover Senate financial disclosures or Executive Branch filings?+
Can I search or list all available filing IDs through the API?+
filing_id directly; there is no search or listing endpoint that enumerates available filings. You can fork this API on Parse and revise it to add a filing search endpoint that accepts member name or date range parameters.