<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alvaro Sacasa</title>
    <description>The latest articles on DEV Community by Alvaro Sacasa (@alvaro_sacasa_fcc0f11d60d).</description>
    <link>https://dev.to/alvaro_sacasa_fcc0f11d60d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3684996%2F640577b5-27e8-4dfb-8690-b3b4b95c801c.jpg</url>
      <title>DEV Community: Alvaro Sacasa</title>
      <link>https://dev.to/alvaro_sacasa_fcc0f11d60d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alvaro_sacasa_fcc0f11d60d"/>
    <language>en</language>
    <item>
      <title>I built a tool to track US Political Donations (and won an award for it)</title>
      <dc:creator>Alvaro Sacasa</dc:creator>
      <pubDate>Mon, 29 Dec 2025 21:11:38 +0000</pubDate>
      <link>https://dev.to/alvaro_sacasa_fcc0f11d60d/i-built-a-tool-to-track-us-political-donations-and-won-an-award-for-it-14k3</link>
      <guid>https://dev.to/alvaro_sacasa_fcc0f11d60d/i-built-a-tool-to-track-us-political-donations-and-won-an-award-for-it-14k3</guid>
      <description>&lt;p&gt;The Problem with "Public" Data&lt;/p&gt;

&lt;p&gt;We all know that government data is technically "public," but that doesn't mean it's accessible. If you've ever tried to pull large datasets from government portals, you know the pain: antiquated UIs, weird CSV exports, and complex pagination.&lt;/p&gt;

&lt;p&gt;I wanted to solve this for US Campaign Finance data. Journalists and researchers need to see who is funding whom, but they often spend more time cleaning data than analyzing it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Solution: Wrapping the OpenFEC API&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We built the FEC Campaign Finance Scraper, an Apify Actor that wraps the official OpenFEC API to make this data consumable at scale.&lt;/p&gt;

&lt;p&gt;Instead of writing custom scripts for every query, developers and researchers can now just input their parameters (committee IDs, date ranges, etc.) and get back clean, structured JSON.&lt;/p&gt;

&lt;p&gt;Key Technical Challenges we solved:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pagination Hell: Automating the deep pagination required to fetch thousands of contribution records.&lt;/li&gt;
&lt;li&gt;Rate Limiting: Handling the FEC's API limits gracefully so the scraper doesn't get blocked mid-job.&lt;/li&gt;
&lt;li&gt;Data Normalization: structuring the output so it's ready for visualization libraries or SQL databases immediately.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The Unexpected Win!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We built this primarily to help the ecosystem, but this week we received some amazing validation. Apify selected our project as the winner of their "Social Good" Spotlight!&lt;/p&gt;

&lt;p&gt;It was a great reminder that as developers, our side projects can have a real impact on transparency and democracy. It’s not always about building the next SaaS, sometimes it’s about making information free.&lt;/p&gt;

&lt;p&gt;Try it out&lt;/p&gt;

&lt;p&gt;If you are building in the Civic Tech or GovTech space, I’d love for you to stress-test it.&lt;/p&gt;

&lt;p&gt;The Actor: &lt;a href="https://apify.com/parseforge/fec-campaign-finance-contributions-scraper" rel="noopener noreferrer"&gt;https://apify.com/parseforge/fec-campaign-finance-contributions-scraper&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The Goal: To help journalists track money in politics without needing a CS degree.&lt;/p&gt;

&lt;p&gt;Question for the community: Have you worked with other government APIs? Which ones are the most painful to integrate? I’m looking for our next project!&lt;/p&gt;

</description>
      <category>automation</category>
    </item>
  </channel>
</rss>
