Automate OpenFEC
HumDay reads OpenFEC’s own published API description and derives 91 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What OpenFEC is
This application programming interface (API) allows you to explore the way candidates and committees fund their campaigns. The Federal Election Commission (FEC) API is a RESTful web service supporting full-text and field-specific searches on FEC data. [Bulk downloads](https://www.fec.gov/data/advanced/?tab=bulk-data) are available on the current site. Information is tied to the underlying forms by
What HumDay can read from OpenFEC
These are the operations a schedule or a trigger can watch.
- GETCombines the election and reporting dates with Commission meetings, conferences, outreach, Advisory Opinions, rules, litigation dates and other events into one calendar.
/calendar-dates/ - GETSearch legal documents by document type, or across all document types using keywords, parameter values and ranges.
/legal/search/ - GETList elections by cycle, office, state, and district.
/elections/search/ - GETSchedule E covers the line item expenditures for independent expenditures.
/schedules/schedule_e/ - GETAll official records and reports filed by or delivered to the FEC.
/filings/ - GETBasic information about electronic files coming into the FEC, posted as they are received.
/efile/filings/ - GETSearch for candidates or committees by name.
/names/candidates/ - GETSearch for candidates or committees by name.
/names/committees/ - GETFetch basic information about candidates and their principal committees.
/candidates/search/ - GETList elections by cycle, office, state, and district.
/elections/summary/ - GETSchedule B filings describe itemized disbursements.
/schedules/schedule_b/ - GETSchedule C shows all loans, endorsements and loan guarantees a committee receives or makes.
/schedules/schedule_c/ - GETSchedule D, it shows debts and obligations owed to or by the committee that are required to be disclosed.
/schedules/schedule_d/ - GETSchedule F, it shows all special expenditures a national or state party committee makes in connection with the general election campaigns of federal candidates.
/schedules/schedule_f/ - GETReturns CSV or ICS for downloading directly into calendar applications like Google, Outlook or other applications.
/calendar-dates/export/ - GETThis endpoint provides information about a committee's Form 3, Form 3X, or Form 3P financial reports, which are aggregated by two-year period.
/totals/{entity_type}/ - GETEach report represents the summary information from Form 3, Form 3X and Form 3P.
/reports/{entity_type}/ - GETEfiling endpoints provide real-time campaign finance data received from electronic filers.
/schedules/schedule_a/efile/ - GETEfiling endpoints provide real-time campaign finance data received from electronic filers.
/schedules/schedule_b/efile/ - GETEfiling endpoints provide real-time campaign finance data received from electronic filers.
/schedules/schedule_e/efile/ - GETLook at the top-level financial information for all candidates running for the same office.
/elections/ - GETFetch basic information about candidates, and use parameters to filter results to the candidates you're looking for.
/candidates/ - GETFetch basic information about committees and filers.
/committees/ - GETUse this endpoint to look up the RAD Analyst for a committee.
/rad-analyst/ - GETSchedule B disbursements aggregated by disbursement purpose category.
/schedules/schedule_b/by_purpose/ - GETSchedule B disbursements aggregated by recipient name.
/schedules/schedule_b/by_recipient/ - GETSchedule E receipts aggregated by recipient candidate.
/schedules/schedule_e/by_candidate/ - GETFEC election dates since 1995.
/election-dates/ - GETAn electioneering communication is any broadcast, cable or satellite communication that fulfills each of the following conditions: The communication refers to a clearly identified…
/electioneering/ - GETThe Operations log contains details of each report loaded into the database.
/operations-log/ - GETFEC election dates since 1995.
/reporting-dates/ - GETSchedule B disbursements aggregated by recipient committee ID, if applicable.
/schedules/schedule_b/by_recipient_id/ - GET52 U.S.C. 30118 allows "communications by a corporation to its stockholders and executive or administrative personnel and their families or by a labor organization to its members…
/communication_costs/ - GETState laws and procedures govern elections for state or local offices as well as how candidates appear on election ballots.
/state-election-office/ - GETSchedule B filings describe itemized disbursements.
/schedules/schedule_b/{sub_id}/ - GETSchedule C shows all loans, endorsements and loan guarantees a committee receives or makes.
/schedules/schedule_c/{sub_id}/ - GETSchedule D, it shows debts and obligations owed to or by the committee that are required to be disclosed.
/schedules/schedule_d/{sub_id}/ - GETSchedule F, it shows all special expenditures a national or state party committee makes in connection with the general election campaigns of federal candidates.
/schedules/schedule_f/{sub_id}/ - GETThis endpoint provides information about a committee's Form 3, Form 3X, or Form 3P financial reports, which are aggregated by two-year period.
/candidate/{candidate_id}/totals/ - GETThis endpoint provides information about a committee's Form 3, Form 3X, or Form 3P financial reports, which are aggregated by two-year period.
/committee/{committee_id}/totals/ - GETAll official records and reports filed by or delivered to the FEC.
/candidate/{candidate_id}/filings/ - GETAll official records and reports filed by or delivered to the FEC.
/committee/{committee_id}/filings/ - GETEach report represents the summary information from Form 3, Form 3X and Form 3P.
/committee/{committee_id}/reports/ - GETProvides cumulative receipt totals by entity type, over a two year cycle.
/totals/by_entity/ - GETAggregated candidate receipts and disbursements grouped by cycle.
/candidates/totals/ - GETThis description is for both /schedules/schedulea/ and /schedules/schedulea/{subid}/.
/schedules/schedule_a/ - GETElectioneering communications costs aggregates
/electioneering/aggregates/ - GETElectioneering costs aggregated by candidate
/electioneering/by_candidate/ - GETCommunication cost aggregated by candidate ID and committee ID.
/communication_costs/aggregates/ - GETCoverage end date per candidate.
/presidential/coverage_end_date/ - GETFinancial summary per candidate.
/presidential/financial_summary/ - GETCommunication cost aggregated by candidate ID and committee ID.
/communication_costs/by_candidate/ - GETThis endpoint is useful for finding detailed information about a particular candidate.
/candidate/{candidate_id}/ - GETThis endpoint is useful for finding detailed information about a particular committee or filer.
/committee/{committee_id}/ - GETKey financial data reported periodically by committees as they are reported.
/efile/reports/pac-party/ - GETKey financial data reported periodically by committees as they are reported.
/efile/reports/house-senate/ - GETKey financial data reported periodically by committees as they are reported.
/efile/reports/presidential/ - GETAggregated candidate receipts and disbursements grouped by office by cycle.
/candidates/totals/by_office/ - GETThis endpoint provides itemized individual contributions received by a committee, aggregated by the contributor’s ZIP code.
/schedules/schedule_a/by_zip/ - GETCandidate total receipts and disbursements aggregated by aggregateby.
/candidates/totals/aggregates/ - GETThis endpoint provides individual contributions received by a committee, aggregated by size: - $200 and under - $200.01 - $499.99 - $500 - $999.99 - $1000 - $1999.99 - $2000 + The…
/schedules/schedule_a/by_size/ - GETThis endpoint provides itemized individual contributions received by a committee, aggregated by the contributor’s state.
/schedules/schedule_a/by_state/ - GETThis endpoint provides itemized individual contributions received by a committee, aggregated by the contributor’s employer name.
/schedules/schedule_a/by_employer/ - GETTotal electioneering communications spent on candidates by cycle or candidate election year
/electioneering/totals/by_candidate/ - GETContribution receipts by size per candidate.
/presidential/contributions/by_size/ - GETThis endpoint provides itemized individual contributions received by a committee, aggregated by the contributor’s occupation.
/schedules/schedule_a/by_occupation/ - GETContribution receipts by state per candidate.
/presidential/contributions/by_state/ - GETTotal communications costs aggregated across committees on supported or opposed candidates by cycle or candidate election year.
/communication_costs/totals/by_candidate/ - GETNet receipts per candidate.
/presidential/contributions/by_candidate/ - GETThis description is for both /schedules/schedulea/ and /schedules/schedulea/{subid}/.
/schedules/schedule_a/{sub_id}/ - GETFind out a candidate's characteristics over time.
/candidate/{candidate_id}/history/ - GETExplore a filer's characteristics over time.
/committee/{committee_id}/history/ - GETThis endpoint is useful for finding detailed information about a particular committee or filer.
/candidate/{candidate_id}/committees/ - GETThis endpoint is useful for finding detailed information about a particular candidate.
/committee/{committee_id}/candidates/ - GETAggregated candidate receipts and disbursements grouped by office by party by cycle.
/candidates/totals/by_office/by_party/ - GETThis endpoint provides itemized individual contributions received by a committee, aggregated by contributor’s state, committee type and cycle.
/schedules/schedule_a/by_state/totals/ - GETTotal independent expenditure on supported or opposed candidates by cycle or candidate election year.
/schedules/schedule_e/totals/by_candidate/ - GETThis endpoint provides itemized individual contributions received by a committee, aggregated by size of contribution and candidate.
/schedules/schedule_a/by_size/by_candidate/ - GETThis endpoint provides itemized individual contributions received by a committee, aggregated by contributor’s state and candidate.
/schedules/schedule_a/by_state/by_candidate/ - GETExplore a filer's characteristics over time.
/candidate/{candidate_id}/committees/history/ - GETFind out a candidate's characteristics over time.
/committee/{committee_id}/candidates/history/ - GETItemized individual contributions aggregated by contributor’s state, candidate, committee type and cycle.
/schedules/schedule_a/by_state/by_candidate/totals/ - GETFind out a candidate's characteristics over time.
/candidate/{candidate_id}/history/{cycle}/ - GETExplore a filer's characteristics over time.
/committee/{committee_id}/history/{cycle}/ - GETExplore a filer's characteristics over time.
/candidate/{candidate_id}/committees/history/{cycle}/ - GETFind out a candidate's characteristics over time.
/committee/{committee_id}/candidates/history/{cycle}/ - GETThis lists the options for the categories and subcategories available in the /audit-search/ endpoint.
/audit-category/ - GETThis lists the options for the primary categories available in the /audit-search/ endpoint.
/audit-primary-category/ - GETSearch for candidates or committees by name.
/names/audit_candidates/ - GETSearch for candidates or committees by name.
/names/audit_committees/ - GETThis endpoint contains Final Audit Reports approved by the Commission since inception.
/audit-case/
How automating OpenFEC works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live OpenFEC account.
- Grant access, then go live. You approve the specific OpenFEC operations it may use — and only those.
Popular OpenFEC integrations
Connect OpenFEC to the tools people pair it with most.
- OpenFEC and OData for namespace microsoft.graphintegration
- OpenFEC and Cloudflareintegration
- OpenFEC and NetBoxintegration
- OpenFEC and GitHubintegration
- OpenFEC and Mistintegration
- OpenFEC and Loket.nlintegration
- OpenFEC and Atlassian The Jira Cloud platformintegration
- OpenFEC and Magento B2Bintegration
- OpenFEC and Stripeintegration
- OpenFEC and Zuora Reference Billingintegration
- OpenFEC and bunqintegration
- OpenFEC and DocuSignintegration
Automate OpenFEC with these
- Monarchinitiative BioLink164 operations
- UniCourt Enterprise158 operations
- OSF APIv2 Documentation156 operations
- IllumiDesk143 operations
- Figshare136 operations
- MCW Rat Genome Database100 operations
- U.S. EPA Enforcement and Compliance History Online (ECHO) Detailed Facility Report (DFR)94 operations
- NBA Stats83 operations
- Thebluealliance The Blue Alliance65 operations
- eDRV57 operations
- Collegefootballdata College Football Data51 operations
- Dnd5eapi D&D 5e47 operations
Categories
Questions about OpenFEC automation
- Can HumDay connect to OpenFEC?
- Yes. HumDay reads OpenFEC's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 91 operations are documented.
- Do I need to write code to automate OpenFEC?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your OpenFEC account.
- What can HumDay do in OpenFEC?
- 0 of the 91 documented operations change something in OpenFEC, and 91 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my OpenFEC account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to OpenFEC is held behind that approval.
Where this came from
The operations above are read from a published API description for OpenFEC at api.open.fec.gov/swagger/. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.