Congressional Trades API (beta)

The EODHD Congressional Trades API returns stock-trade disclosures filed by members of the US Congress. Under the STOCK Act, senators and representatives must publicly disclose their securities transactions within 45 days. EODHD collects these filings directly from the two official government portals — the Senate Electronic Financial Disclosure system and the House Clerk disclosure site — normalises them into a single schema, and serves both chambers through one endpoint.

Each record pairs the trading member with the traded asset and the transaction, and adds fields the raw filings do not provide directly: numeric bounds parsed from the disclosed amount range, the number of days between the trade and its disclosure, a flag for filings that missed the 45-day window, and a link back to the original filing for verification.

Overview

The endpoint is reached over HTTPS with a GET request and authenticated by an api_token query parameter, the same token used across the EODHD API. It returns a JSON object with three top-level keys: data (the array of trade records), meta (the number of rows matching the filter across all pages, plus the offset and limit of the page you received), and links (the path of the next page, when one exists). Results are paged with page[offset] and page[limit], where the default page size is 20 rows and the maximum is 100.

https://eodhd.com/api/congressional-trades?api_token=YOUR_TOKEN

Records are always returned newest first, ordered by transaction date descending. The order is fixed — there is no sort parameter, so narrow a result set with the filters below rather than by re-ordering it. A handful of filings carry a mistyped transaction date that falls in the future, and descending order puts them at the very top of an unfiltered request, so set transaction_date_to to today’s date when you want a clean first page. JSON is the only output format; there is no fmt parameter, and any unrecognised query parameter is ignored rather than rejected.

Coverage and History

History goes back to the first electronic periodic transaction reports published under the STOCK Act, which took effect in 2012. Both chambers appear from 2012 onwards, with sparse coverage before 2014 while electronic filing was still being adopted. The figures below were measured in August 2026 and grow with every new filing.

Annual volume is sparse at the start and then becomes continuous: 2012 contributes 8 trades and 2013 contributes 123. From 2014 the record runs without gaps — 1,486 trades that year, then roughly 2,900 to 4,800 per year through 2024, with 2025 the heaviest year so far at 7,379. For a study that needs a uniform history, 2014 is the practical starting point; 2012 and 2013 are better treated as a fragment than as full years.

Every count above can be reproduced from the API itself, so you never have to rely on this page being current. Request a date window and read total from the meta object — this returns the number of trades that took place during the 2025 calendar year:

https://eodhd.com/api/congressional-trades?api_token=YOUR_TOKEN&transaction_date_from=2025-01-01&transaction_date_to=2025-12-31&page%5Blimit%5D=1

Freshness follows the source, not the market. A trade appears once the member files it, and the STOCK Act allows up to 45 days for that, so the newest transaction date in the feed trails the current date by days to weeks. Filings are collected four times on each weekday, at 00:00, 06:00, 12:00 and 19:00 UTC, with a separate reconciliation pass at 03:00 UTC that re-reads recent filings and picks up amendments.

Request

All parameters are optional except api_token. Filters combine with logical AND, and the member, date-range, symbol, and transaction-type filters can be used together to narrow the result set.

Parameters

Request Example

URL cURL PHP Python R Chat GPT

https://eodhd.com/api/congressional-trades?api_token=YOUR_TOKEN&chamber=senate&transaction_type=purchase,sale&transaction_date_from=2026-01-01&page[limit]=5

(Sign up for free to get an API token)

curl --location "https://eodhd.com/api/congressional-trades?api_token=YOUR_TOKEN&chamber=senate&transaction_type=purchase,sale&transaction_date_from=2026-01-01&page[limit]=5&fmt=json"

(Sign up for free to get an API token)

$curl = curl_init();

curl_setopt_array($curl, array(
    CURLOPT_URL => 'https://eodhd.com/api/congressional-trades?api_token=YOUR_TOKEN&chamber=senate&transaction_type=purchase,sale&transaction_date_from=2026-01-01&page[limit]=5&fmt=json',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_ENCODING => '',
    CURLOPT_MAXREDIRS => 10,
    CURLOPT_TIMEOUT => 0,
    CURLOPT_FOLLOWLOCATION => true,
    CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
    CURLOPT_CUSTOMREQUEST => 'GET',
));

$data = curl_exec($curl);
curl_close($curl);

try {
    $data = json_decode($data, true, 512, JSON_THROW_ON_ERROR);
    var_dump($data);
} catch (Exception $e) {
    echo 'Error. '.$e->getMessage();
}

(Sign up for free to get an API token)

import requests

url = f'https://eodhd.com/api/congressional-trades?api_token=YOUR_TOKEN&chamber=senate&transaction_type=purchase,sale&transaction_date_from=2026-01-01&page[limit]=5&fmt=json'
data = requests.get(url).json()

print(data)

(Sign up for free to get an API token)

library(httr)
library(jsonlite)

url <- 'https://eodhd.com/api/congressional-trades?api_token=YOUR_TOKEN&chamber=senate&transaction_type=purchase,sale&transaction_date_from=2026-01-01&page[limit]=5&fmt=json'
response <- GET(url)

if (http_type(response) == "application/json") {
    content <- content(response, "text", encoding = "UTF-8")
    cat(content)
} else {
    cat("Error while receiving data\n")
}

(Sign up for free to get an API token)

New to coding? Our ChatGPT assistant can generate code in any language tailored to our API. Simply describe how you want to use our data, and get a working piece of code. Don’t forget to replace the API token with your own.

Try it now (it's free)!

How to use it (YouTube)

Response

Each record carries a top-level chamber field and four nested objects: member, asset, transaction, and source. The example below is a single record; a real response returns an array under data.

Response Example

{
  "data": [
    {
      "chamber": "senate",
      "member": {
        "bioguide_id": "W000802",
        "first_name": "Sheldon",
        "last_name": "Whitehouse",
        "full_name": "Sheldon Whitehouse",
        "office": "Whitehouse, Sheldon (Senator)",
        "state": null,
        "party": null,
        "district": null
      },
      "asset": {
        "symbol": "NVDA",
        "description": "NVIDIA Corporation - Common Stock",
        "asset_type": "Stock"
      },
      "transaction": {
        "type": "sale",
        "transaction_date": "2026-06-30",
        "disclosure_date": "2026-07-08",
        "owner": "Self",
        "amount_range": "$15,001 - $50,000",
        "amount_low": 15001,
        "amount_high": 50000,
        "days_to_disclose": 8,
        "is_late": false,
        "comment": null
      },
      "source": {
        "filing_url": "https://efdsearch.senate.gov/search/view/ptr/5d9b1b8e-2ae1-442b-860c-e79b8a701dc6/",
        "source_system": "senate",
        "filing_identifier": "5d9b1b8e-2ae1-442b-860c-e79b8a701dc6"
      }
    }
  ],
  "meta": { "total": 45561, "page": { "offset": 0, "limit": 20 } },
  "links": { "next": "/api/congressional-trades?page%5Boffset%5D=20&page%5Blimit%5D=20" }
}

The next link is a path relative to the API host, with the pagination brackets URL-encoded. Prefix it with https://eodhd.com and add your api_token to fetch the following page. The next key is absent on the last page, which is the signal to stop paging.

Response Fields

Sign up & Get Data

Response Codes

Notes and Limitations

• Both chambers are returned together. Use chamber=senate or chamber=house to restrict to one; the chamber field on each record identifies its origin.
• Exchanges are rare. Purchases and sales are split almost evenly across the history — roughly 23,000 each — while the exchange type accounts for 316 records in total, so a filter on it returns a small set by nature.
• The amount_low and amount_high fields are parsed from the disclosed amount band; days_to_disclose and is_late are computed against the 45-day STOCK Act window. These are provided by EODHD and are not part of the raw filing.
• Some holdings, including many bonds and other instruments, carry no ticker symbol. For those records asset.symbol is null while asset.description and asset.asset_type remain populated, and a request filtered by symbol will not return them.
• Source data is reproduced as filed. Member details such as state are populated only where the source provides them, and data-entry errors in the original disclosures are passed through rather than silently corrected. The filing_url on each record links to the official source for verification.
• 82 records carry a mistyped transaction date that falls in the future, the most extreme in the year 3031. They are copied from the filings as submitted, and because results are ordered by transaction date descending they surface on the first unfiltered page. Set transaction_date_to to today’s date to exclude them.
• Disclosure timing is set by the filer, not by EODHD. The STOCK Act allows up to 45 days between a trade and its disclosure, and late filings occur, so treat this data as a disclosure record rather than a real-time signal.

Related APIs

• Insider Transactions API — the corporate counterpart: trades filed by company officers and directors on SEC Form 4.
• SEC Filings API — the filings themselves, for readers who need the underlying disclosure documents.
• End-of-Day Historical Data API — prices to join to a trade, for measuring what a disclosed transaction was worth or how the stock moved afterwards.
• Search API — resolve a company name from a filing into the ticker to pass as symbol.
• Sanctions API — another compliance and screening dataset built on official government sources.