# FEC Campaign Contributions by Donor, Employer and State (`talcoe/fec-contributions`) Actor

Pull itemized FEC campaign contributions filtered by donor name, employer, state, election cycle and minimum amount, with recipient committee and candidate, billed per result.

- **URL**: https://apify.com/talcoe/fec-contributions.md
- **Developed by:** [M Usama](https://apify.com/talcoe) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does FEC Campaign Contributions Scraper do?

It returns itemized individual campaign contributions filed with the US Federal Election Commission (FEC). Filter by donor name, employer, donor state, election cycle and minimum amount. Each record has the donor, employer, occupation, city, state, amount, date, the recipient committee (and candidate when listed), the report type and a link to the original filing. Filters keep runs small, and pricing is per result.

### Data source

The Actor reads the public OpenFEC JSON API (`api.open.fec.gov`, Schedule A itemized receipts), which the FEC updates as committees file their reports.

### Why use it?

- Prospect research: find donors by employer or state and see who they give to and how much.
- Compliance and due diligence: check political giving by an executive, employee group or company.
- Journalism and research: track giving to a committee or from an industry across a cycle.
- Replaces manual searching on fec.gov and hand built API pagination.

### How to use it

1. Open the Actor and set the filters.
2. Click Start. Download results as JSON, CSV or Excel, or read them through the API.
3. Add a Schedule and an Integration (Slack, Google Sheets, webhook) to get new records automatically.

### Input

| Field | Description |
|---|---|
| `contributorName` | Last name, first name, or part of the donor name, e.g. `SMITH, JOHN`. |
| `contributorEmployer` | Employer as reported on the filing, e.g. `Google`. Partial match. |
| `contributorState` | Two letter donor state code, e.g. `CA`. |
| `cycle` | Two year election cycle, named for its even end year. Default `2024`. |
| `minAmount` | Only contributions of at least this many US dollars. |
| `maxResults` | Hard stop for the run. You are billed per result, so this caps the cost. |
| `proxyConfiguration` | Apify proxy is recommended for larger runs. |

Example input:

```json
{ "contributorEmployer": "Google", "cycle": "2024", "minAmount": 1000, "maxResults": 50 }
```

### Output

Every record has the same shape:

```json
{
  "id": "4020620251143681804",
  "contributorName": "YU, KAIWEN",
  "amount": 3300,
  "date": "2024-12-31",
  "employer": "GOOGLE",
  "occupation": "SOFTWARE DEVELOPMENT ENGINEER",
  "city": "SEATTLE",
  "state": "WA",
  "zip": "981034117",
  "recipientCommittee": "FRIENDS OF BERNIE SANDERS",
  "recipientCommitteeId": "C00411330",
  "recipientCommitteeType": "Senate",
  "yearToDateTotal": 3300,
  "receiptType": "EARMARKED CONTRIBUTION",
  "cycle": 2024,
  "filingUrl": "https://docquery.fec.gov/cgi-bin/fecimg/?202501319748835541"
}
```

| Field | Meaning |
|---|---|
| `id` | FEC sub id, stable and safe for deduplication between runs |
| `contributorName` | Donor name as filed (LAST, FIRST) |
| `amount` | Contribution amount in US dollars |
| `date` | Receipt date, ISO format |
| `employer`, `occupation` | As reported by the donor |
| `city`, `state`, `zip` | Donor address fields |
| `recipientCommittee`, `recipientCommitteeId`, `recipientCommitteeType` | Committee that received the filing |
| `candidateName`, `candidateId`, `candidateOffice` | Candidate, when the filing names one |
| `yearToDateTotal` | Donor's aggregate to that committee for the year |
| `receiptType`, `electionType`, `electionYear` | FEC classification of the receipt |
| `memo`, `isMemo` | Memo text and whether the line is a memo entry |
| `filingUrl` | Link to the original filing image |

### Pricing

Pay per event: a small fee when a run starts, then a fixed price per result returned. You only pay for records that pass your filters. Set `maxResults` to cap any run.

### Limitations

- Itemized individual contributions only (Schedule A). Small unitemized donations are not published by name.
- Results are newest first within the chosen cycle.
- Names, employers and addresses are exactly as filed, so spelling varies between filings.
- Contributions routed through conduits such as ActBlue list the recipient committee in `recipientCommittee`; the conduit appears in the filing link.
- The FEC API enforces rate limits, so very large runs can be slow.

### FAQ

**Is this legal?** The Actor reads data the FEC publishes openly through its public API. Federal law restricts using contributor data to solicit contributions or for commercial purposes unrelated to elections, so you are responsible for how you use it.

**Something is missing or broken?** Open an issue in the Issues tab; response time is usually under a day.

# Actor input Schema

## `contributorName` (type: `string`):

Last name, first name, or any part of the donor name, e.g. SMITH, JOHN. Leave empty for all donors.

## `contributorEmployer` (type: `string`):

Employer as reported on the filing, e.g. Google. Matches partial text.

## `contributorState` (type: `string`):

Two letter state code of the donor, e.g. CA. Leave empty for all states.

## `cycle` (type: `string`):

Two year transaction period, named for the even year it ends in.

## `minAmount` (type: `integer`):

Only contributions of at least this amount.

## `maxResults` (type: `integer`):

Hard stop for the run. You are billed per result, so this caps the cost.

## `proxyConfiguration` (type: `object`):

Apify proxy is recommended for larger runs.

## Actor input object example

```json
{
  "contributorEmployer": "Google",
  "cycle": "2024",
  "minAmount": 1000,
  "maxResults": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "contributorEmployer": "Google",
    "cycle": "2024",
    "minAmount": 1000,
    "maxResults": 50,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("talcoe/fec-contributions").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 = {
    "contributorEmployer": "Google",
    "cycle": "2024",
    "minAmount": 1000,
    "maxResults": 50,
    "proxyConfiguration": { "useApifyProxy": False },
}

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

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

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

```

## CLI example

```bash
echo '{
  "contributorEmployer": "Google",
  "cycle": "2024",
  "minAmount": 1000,
  "maxResults": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call talcoe/fec-contributions --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,talcoe/fec-contributions"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ioskXH5LHgBLYYT3C/builds/eYVe1fVTSRTwhT0g6/openapi.json