# FEC Committee Monitor — New Campaign Committee Registrations (`eschalon/fec-committee-monitor`) Actor

Track newly registered US federal campaign committees (House, Senate, PACs, Super PACs, party committees) straight from official FEC data, with treasurer, party, state, and registration links.

- **URL**: https://apify.com/eschalon/fec-committee-monitor.md
- **Developed by:** [Corey Kuwanoe](https://apify.com/eschalon) (community)
- **Categories:** News, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## FEC Committee Monitor

Track **newly registered US federal campaign committees** — House and Senate campaigns, PACs, Super PACs, and party committees — straight from the official Federal Election Commission API.

Every 2026 midterm campaign starts the same way: a Statement of Organization (Form 1) filed with the FEC. This actor surfaces those registrations within days of filing, before they show up anywhere else.

### Who uses this

- **Journalists** — spot new candidates and Super PACs the moment they organize
- **Political consultants & vendors** — new committees are new prospects with fresh budgets
- **Researchers & watchdogs** — track committee formation trends by state, party, and type
- **Fundraising platforms** — reach campaigns early in their lifecycle

### What you get

One dataset row per newly registered committee:

| Field | Example |
|---|---|
| `committee_id` | `C00901234` |
| `name` | `FRIENDS OF JANE DOE` |
| `committee_type` / `committee_type_full` | `H` / `House` |
| `designation_full` | `Principal campaign committee` |
| `state` | `TX` |
| `party_full` | `Democratic Party` |
| `treasurer_name` | `SMITH, JOHN` |
| `first_file_date` | `2026-06-30` |
| `registration_url` | Link to the committee's page on fec.gov |

### Input

- **apiKey** — free api.data.gov key ([sign up here](https://api.data.gov/signup/), takes 1 minute). Defaults to `DEMO_KEY`, which works for a quick try but is heavily rate-limited.
- **sinceDays** — look-back window (default 7 days)
- **committeeTypes** — optional filter: `H` House, `S` Senate, `P` Presidential, `N`/`Q` PACs, `O` Super PAC, `X`/`Y` party committees, `I` independent expenditure filers
- **states** — optional two-letter state filters
- **maxItems** — cap on results (default 500)

### Typical setups

- **Weekly new-committee digest**: schedule weekly, `sinceDays: 7`, export to email/Slack/Sheets via Apify integrations.
- **Super PAC watch**: `committeeTypes: ["O"]`, `sinceDays: 30`.
- **State delegation tracker**: `states: ["PA"]`, `committeeTypes: ["H", "S"]`.

### Data source & legality

Data comes from the FEC's official public API (`api.open.fec.gov`). This is public-record data published by the US government; no scraping, no ToS issues, no PII beyond what federal law requires committees to disclose.

# Actor input Schema

## `apiKey` (type: `string`):

Your free api.data.gov key for the FEC API (get one at https://api.data.gov/signup/). Defaults to DEMO\_KEY, which is heavily rate-limited — fine for trying the actor, not for production monitoring.

## `sinceDays` (type: `integer`):

Return committees whose first FEC filing was within this many days.

## `committeeTypes` (type: `array`):

Optional FEC committee type codes: H (House), S (Senate), P (Presidential), N (PAC, non-qualified), Q (PAC, qualified), O (Super PAC), X/Y (party committees), I (independent expenditure filer). Leave empty for all types.

## `states` (type: `array`):

Optional two-letter state codes to filter by (e.g. TX, PA). Leave empty for all states.

## `maxItems` (type: `integer`):

Stop after this many committees.

## Actor input object example

```json
{
  "apiKey": "DEMO_KEY",
  "sinceDays": 7,
  "maxItems": 500
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("eschalon/fec-committee-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("eschalon/fec-committee-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call eschalon/fec-committee-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=eschalon/fec-committee-monitor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/N77abbl61zdSpUR1E/builds/0e05XRCj67DcS2RDO/openapi.json