The full congressional dataset
Every row behind the feed is published here as plain JSON: 75,064 disclosures (72,011 transactions and 3,053 paper filings), cut into 29 parts across 15 filing years, 21.6 MiB in total. Downloading every part below gives you the complete corpus for build 20260914.2 — nothing is sampled, summarised or withheld from it.
The parts are contiguous and already in the site's own feed order (newest filing date first, transactions before paper filings within a date), so concatenating their rows arrays in the order listed reproduces the dataset exactly. Each part names its ownoffset, so the reassembly can be checked rather than trusted.The machine-readable indexlists every part with its row counts, byte size and first/last row key.
Why parts, and not one file. This dataset was previously served as a single feed.v1.json. It reached 22,382,648 bytes — 85.4% of the 25 MiB per-asset limit our static host enforces on every plan — and was growing by roughly 9,287 disclosures a year. A single file would have become undeployable, taking the whole site's next release with it. Each part below is bounded at 1024.0 KiB, so the corpus can now grow without any one asset approaching that limit. The old path,/congress/data/feed.v1.json, still answers and states its own retirement rather than disappearing.
| Part | Filing year | Rows | Transactions | Offset | Size |
|---|---|---|---|---|---|
| 2026-1.v1.json | 2026 | 3,238 | 3,199 | 0 | 1023.8 KiB |
| 2026-2.v1.json | 2026 | 1,938 | 1,917 | 3,238 | 592.6 KiB |
| 2025-1.v1.json | 2025 | 3,404 | 3,374 | 5,176 | 1023.7 KiB |
| 2025-2.v1.json | 2025 | 3,381 | 3,354 | 8,580 | 1023.9 KiB |
| 2025-3.v1.json | 2025 | 1,912 | 1,879 | 11,961 | 580.1 KiB |
| 2024-1.v1.json | 2024 | 3,378 | 3,316 | 13,873 | 1023.9 KiB |
| 2024-2.v1.json | 2024 | 145 | 142 | 17,251 | 44.3 KiB |
| 2023-1.v1.json | 2023 | 3,419 | 3,371 | 17,396 | 1023.8 KiB |
| 2023-2.v1.json | 2023 | 1,949 | 1,901 | 20,815 | 584.4 KiB |
| 2022-1.v1.json | 2022 | 3,469 | 3,368 | 22,764 | 1023.8 KiB |
| 2022-2.v1.json | 2022 | 1,156 | 1,122 | 26,233 | 345.9 KiB |
| 2021-1.v1.json | 2021 | 3,512 | 3,435 | 27,389 | 1024.0 KiB |
| 2021-2.v1.json | 2021 | 3,317 | 3,254 | 30,901 | 987.6 KiB |
| 2020-1.v1.json | 2020 | 3,457 | 3,375 | 34,218 | 1024.0 KiB |
| 2020-2.v1.json | 2020 | 3,443 | 3,404 | 37,675 | 1023.8 KiB |
| 2020-3.v1.json | 2020 | 1,571 | 1,521 | 41,118 | 460.7 KiB |
| 2019-1.v1.json | 2019 | 3,476 | 3,346 | 42,689 | 1023.9 KiB |
| 2019-2.v1.json | 2019 | 3,420 | 3,327 | 46,165 | 1016.0 KiB |
| 2018-1.v1.json | 2018 | 3,488 | 3,299 | 49,585 | 1023.8 KiB |
| 2018-2.v1.json | 2018 | 2,456 | 2,296 | 53,073 | 719.2 KiB |
| 2017-1.v1.json | 2017 | 3,515 | 3,279 | 55,529 | 1024.0 KiB |
| 2017-2.v1.json | 2017 | 2,032 | 1,934 | 59,044 | 584.2 KiB |
| 2016-1.v1.json | 2016 | 3,501 | 3,287 | 61,076 | 1023.9 KiB |
| 2016-2.v1.json | 2016 | 2,074 | 1,925 | 64,577 | 586.6 KiB |
| 2015-1.v1.json | 2015 | 3,518 | 3,280 | 66,651 | 1023.9 KiB |
| 2015-2.v1.json | 2015 | 1,847 | 1,717 | 70,169 | 528.4 KiB |
| 2014-1.v1.json | 2014 | 2,819 | 2,389 | 72,016 | 762.6 KiB |
| 2013-1.v1.json | 2013 | 169 | 0 | 74,835 | 26.2 KiB |
| 2012-1.v1.json | 2012 | 60 | 0 | 75,004 | 9.5 KiB |
Largest part in this build: 1024.0 KiB, against a 1024.0 KiB ceiling the build enforces — a build that could not fit a part under it fails rather than publishing an oversized asset.