Congress API Update

The U.S. Capitol (Nicholas Kamm/AFP/Getty Images)

When we took over projects from the Sunlight Foundation last year, we inherited an Application Programming Interface, or API, that overlapped with one of our own.

Sunlight’s Congress API and ProPublica’s Congress API are similar enough that we decided to try to merge them together rather than run them separately, and to do so in a way that makes as few users change their code as possible.

Today we’ve got an update on our progress.

Users of the ProPublica Congress API can now access additional fields in responses for Members, Bills, Votes and Nominations. We’ve updated our documentation to provide examples of those responses. These aren’t new responses but existing ones that now include some new attributes brought over from the Sunlight API. Details on those fields are here.

We plan to fold in Sunlight fields and responses for Committees, Hearings, Floor Updates and Amendments, though that work isn’t finished yet.

As part of the merger process, we also need to deprecate a few features: For instance, the combined API will drop a few older attributes, including the unique identifiers for lawmakers that were used by the now-defunct Thomas website. We’ve also removed Facebook numeric IDs (not account names) for lawmakers, owing to changes in the Facebook API. Details on which fields we’re not supporting are here, organized by specific object (Member, Bill, etc.).

We are also deprecating the Sunlight API’s feature that let developers filter on fields within requests. The ProPublica Congress API has a more traditional RESTful style that has only a few query-string options.

Another feature we need to deprecate is the geographic lookup for members and districts. You likely already have moved off of this, as the lookups have been out of date since before we took over the API. They reflect the early part of the previous Congress, before Virginia, North Carolina and Florida approved new congressional maps for House districts.

As an alternative, we are encouraging developers to use the Google Civic Information API, which is what we use in our Represent news application. If you wish to run your own geographic lookup service, you can use the Pentagon codebase that Sunlight originally developed or a more recently updated project called Represent Boundaries.

With that exception, users of the existing Sunlight Congress API will see no change during this time, and we’ll continue to update the data in it.

Once we’ve completed the process of merging in all of the Sunlight responses and fields, we’ll release version 2 of the ProPublica Congress API.

We’ll be adding some brand-new responses to the ProPublica Congress API, too. Among them are public statements by members of Congress, which we’ve already started showing on Represent. In addition to being able to search the titles of these statements, Represent users can browse them on member pages or by popular subjects like “repealing and replacing the Affordable Care Act.”

We welcome your input and feedback at

More from ProPublica

ProPublica2 min read
Hate Getting Parking Tickets in Chicago? Here’s How You Can Start Change-Making Conversations About the City’s Ticketing System.
by Derrick Clifton Chicago’s ticketing system hurts everyone in a variety of ways, and the city’s new mayor, Lori Lightfoot, has promised reforms on tickets, fines and fees that saddle motori
ProPublica17 min readSociety
The Questionable Conviction, and Re-Conviction, of Ricky Joyner
by Christian Sheckler, South Bend Tribune, and Ken Armstrong, ProPublica When an Amish farmer found the body of Sandra Hernandez in a hayfield in LaGrange County, Indiana, on an early spring
ProPublica6 min readSociety
Illinois Lawmakers Demand Child Welfare Officials Better Serve Spanish-Speaking Families
by Duaa Eldeib and Melissa Sanchez Illinois lawmakers and advocates are calling on state child welfare officials to better comply with a federal court order to serve Spanish-speaking families