
FEC Campaign Finance Monitor — Track Filings
Monitor official FEC committee filings by committee ID. Returns recently processed public filing records; does not collect contributor lists.
FEC Campaign Finance Monitor — Track Filings returns 10 documented output fields, including committeeId, committeeName, reportType, coverageEndDate and filingDate. Every field carries a declared type, a written description and an example value. 18 runs are recorded on Apify.
- 10
- Output fields
- 3
- Inputs
- 18
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| committeeId | string | The Federal Election Commission's identifier for the committee, which starts with C. | C00000001 |
| committeeName | string | Registered name of the committee. | Example for Congress |
| reportType | string | Type of filing, e.g. F3 or F3A. The 'A' variants are amendments to an earlier filing, so counting originals and amendments together double-counts. | F3 |
| coverageEndDate | string | Last day the reporting period covers. | 2026-09-30 |
| filingDate | string | Date the filing was received or processed, when published. | 2026-10-15 |
| totalReceipts | number | Total receipts the committee reported for the period, in US DOLLARS. | 125000.5 |
| totalDisbursements | number | Total disbursements the committee reported for the period, in US DOLLARS. | 98000 |
| cashOnHand | number | Cash the committee reported on hand at the end of the period, in US DOLLARS. | 420000 |
| amendmentIndicator | string | Whether this filing amends an earlier one. Only the latest amendment is current, so summing without checking this double-counts. | A |
| source | string | Which upstream source produced this row. | example-source |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"committeeId": "C00000001",
"committeeName": "Example for Congress",
"reportType": "F3",
"coverageEndDate": "2026-09-30",
"filingDate": "2026-10-15",
"totalReceipts": 125000.5,
"totalDisbursements": 98000,
"cashOnHand": 420000
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| apiKey | stringoptional | Secret — supply your own value. |
| committeeIds | arrayrequired | One or more FEC committee IDs, for example C00401224. |
| perCommittee | integeroptional | Maximum recent filings returned for each committee. |
04 — run
Run FEC Campaign Finance Monitor on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
10 of 10 fields described
- What does FEC Campaign Finance Monitor — Track Filings return?
- It returns 10 documented output fields: committeeId, committeeName, reportType, coverageEndDate, filingDate, totalReceipts, totalDisbursements, cashOnHand, amendmentIndicator and source. Each field declares its type, a description of what it holds, and an example value.
- What input does FEC Campaign Finance Monitor — Track Filings require?
- committeeIds is required. A further 2 inputs are optional. The full input schema, with types and defaults, is below.
- Does FEC Campaign Finance Monitor — Track Filings need an API key or login?
- Yes — apiKey is marked secret and must be supplied by you. Nothing else in the input schema needs credentials.
- How do I run FEC Campaign Finance Monitor — Track Filings?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.