Bulk Data content access about api HOT 8 CLOSED

BILLSTATUS and ECFR content is now available via the API:

https://api.govinfo.gov/collections:

{
"collectionCode": "BILLSTATUS",
"collectionName": "Congressional Bill Status",
"packageCount": 5554,
"granuleCount": null
},
....
{
"collectionCode": "ECFR",
"collectionName": "Electronic Code of Federal Regulations",
"packageCount": 16,
"granuleCount": null
},

We are in the process of reindexing, so the numbers under packageCount will increase over the coming weeks.

You can use the collections and packages endpoints for these packages now.

from api.

I am currently working with the API on a project related to congressional bills. It would be great if I could use the same API to get full bill text in JSON format. It's just easier to work with than working with this type of XML: https://www.govinfo.gov/content/pkg/BILLS-115hr2740rfs/xml/BILLS-115hr2740rfs.xml

from api.

@cnizzardini - thanks for the feedback. As you mentioned, there is no official version of Congressional Bills in JSON format currently.

Have you considered using xml2json or a similar library for your language of choice (PHP, it looks like) to transform the XML into json? Of course, then you're not dealing directly with the official content, so it may require additional verification that the translated version meets your needs.

from api.

We are working on a project studying government documents, and it would be very helpful if we could directly download bulkdata through the API. Thanks!

from api.

@jonquandt Just out of curiosity, is there a way to download the whole corpus before you make the feature available? I know this can be done by downloading though API per file but wanted to make sure this follows your rate limit first :)

from api.

@yian-yin - when you say “whole corpus”, do you mean all of the files available through the bulk data repository, or the entire corpus of content available on govinfo?

The bulk data repository represents only a subset of documents available from govinfo - primarily XML content only.

Via the govinfo API, you can already access much of the xml content that exists on the bulk data repository- like XML of Congressional Bills and the Federal Register. Going via the API for those resources does also give the flexibility of getting other content formats and our MODS metadata records for that content, which provides a wealth of information that can be used to understand the content and link it to other Government publications.

There are a few collections that are available only via the bulk data site, currently. From current usage patterns, we would prioritize making Congressional Billstatus and ECFR data available via the API, though other types might make sense to include as well.

from api.

@jonquandt Thanks for your answer! I am actually interested in the entire corpus of content available on govinfo. As I understand, a large fraction of such information is currently unavailable through bulk data, that's why I ask if there's any rate limit in using API.

Also thanks for reminding me that some collections only exist in the bulk data site -- does this mean the API only includes a subset of what's available on govinfo? If so, would you mind letting me know the estimate of this fraction?

from api.

@yin-yang no rate limit at the moment, but we may impose one if we’re seeing an excessive number of requests - I don’t anticipate it being an issue at this time. Best to try to do larger updates overnight though.

Of the list of collections listed on www.govinfo.gov/bulkdata, the bulk data only collections are:

-Congressional Bill Status – 113th Congress to Present
-Congressional Bill Summaries – House Bill Summaries added in 2014, summaries for Senate Bills added in January 2015
-Electronic Code of Federal Regulations (current XML file for each of the titles in the eCFR)
-Supreme Court Decisions

All of the bulk data resources are available via our bulk data sitemaps or directly as xml or json endpoints.

The vast majority of content and metadata is available via the API.

from api.