Top of page

A screen shot of the API for committee meeting information
Users can return detailed information for a specified committee meeting within the API. The Library of Congress is exploring options related to committee meeting video metadata currently.

An Update on the API

Share this post:

The following is a guest post by Andrew Reiter, a legislative data specialist within the Congressional Research Service (CRS) of the Library of Congress.

Last September, introduced the beta API. Today, we are thrilled to announce that the beta label has been removed from the API. We are very excited about this news and a great deal of hard work has gone on behind the scenes this year to make this happen. As we celebrate the removal of the beta label, we are greatly appreciative of our data partners, the Congressional Data Task Force, and our users.

Since announcing the beta API, the API has added several new endpoints and enhancements that include new endpoints for the daily Congressional Record and the bound Congressional Record. While we have created several new endpoints, existing endpoints continue to be enhanced. For example, the Library of Congress is investigating how to provide all committee video metadata elements from a single data source, the API Committee Meeting endpoint. We expect there will be more collaboration with our data partners, developers, and users on how to create new, useful, and exciting features within the API.

A screenshot of the API that shows parameters
The website allows users to explore available parameters related to particular endpoints

There is a GitHub page for the API where you can get additional information and provide feedback if you encounter any issues, bugs, or difficulties. Our developers and our team greatly appreciate feedback and use this to consider possible changes, fixes, and enhancements to the API. We also encourage users to look at the issues section for information which can help answer possible queries. Additionally, the GitHub repository hosts a Change Log that details past changes to the API and upcoming API development.

A screenshot from GitHub of the API Change Log
The API Change Log, which is available in the GitHub repository, highlights upcoming changes and enhancements to the API.

The collaboration and feedback with our partners and users have greatly improved the API’s collections and usability. We look forward to adding more of’s fantastic collections to the API and making collections more accessible to our users.


With today’s release the enhancements include:

Enhancement – Legislation – Download Amendments First Iteration

  • You can use the Download Results link on the amendments tab of a bill to save a spreadsheet of metadata and text where available. See Coverage Dates for availability of amendment text.
  • You may need to wrap text and resize the Amendment Text column in order to view the text in the downloaded Excel file.
  • Extremely large texts will be incomplete. API

  • The API is no longer in beta as endpoints for all collections have been added.
  • Improvements based on user feedback have been implemented.
  • You can sign up for a key to use the API  to retrieve legislative data in a machine-readable format.

Subscribe to In Custodia Legis – it’s free! – to receive interesting posts drawn from the Law Library of Congress’s vast collections and our staff’s expertise in U.S., foreign, and international law.



Add a Comment

This blog is governed by the general rules of respectful civil discourse. You are fully responsible for everything that you post. The content of all comments is released into the public domain unless clearly stated otherwise. The Library of Congress does not control the content posted. Nevertheless, the Library of Congress may monitor any user-generated content as it chooses and reserves the right to remove content for any reason whatever, without consent. Gratuitous links to sites are viewed as spam and may result in removed comments. We further reserve the right, in our sole discretion, to remove a user's privilege to post content on the Library site. Read our Comment and Posting Policy.

Required fields are indicated with an * asterisk.