LibraryOfCongress / api.congress.gov

congress.gov API
642 stars 39 forks source link

Amendment Actions API Returning 404 #149

Closed YZhang-Jeremy closed 1 year ago

YZhang-Jeremy commented 1 year ago

The amendment actions API has been returning 404s since Friday.

For instance, we requested https://api.congress.gov/v3/amendment/111/HAMDT/787/cosponsors?format=json&offset=0&limit=250&api_key=KEY and the response has always been {"error": "Unknown resource: bill/100/HAMDT/787/actions"} for the last few days.

HAMDT787 is an amendment that does exist: 111 787 SAMDT To end $272 billion in spending on bailouts under TARP and reduce record deficits and levels of debt. https://api.congress.gov/v3/amendment/111/samdt/787?format=json 4/2/09 Amendment SA 787 not agreed to in Senate by Yea-Nay Vote. 28 - 70. Record Vote Number: 134. 2022-02-03T06:10:50Z

It would be greatly appreciated if you could look into this issue!

rbram commented 1 year ago

Hello. Thanks for your feedback.

For the following amendment, the following calls worked for me:

https://api.congress.gov/v3/amendment/111/hamdt/787/actions.json?api_key=INSERT_KEY https://api.congress.gov/v3/amendment/111/hamdt/787/actions?format=json&offset=0&limit=250&api_key=INSERT_KEY

But this doesn’t: https://api.congress.gov/v3/amendment/111/HAMDT/787/actions?format=json&limit=250&api_key=DEMO_KEY

The issue is that the amendment endpoint is lowercase only. So “hamdt” is correct, “HAMDT” is not correct. The guidelines on the api.congress.gov website provide an example of this: The type of amendment. Value can be hamdt, samdt, or suamdt.

Regarding the call for cosponsors of HAmdt 787, there are no cosponsors for 111 HAmdt 787: https://www.congress.gov/amendment/111th-congress/house-amendment/787?s=5&r=1 https://api.congress.gov/v3/amendment/111/hamdt/787/cosponsors.json?api_key=INSERT_KEY

We hope this helps!

YZhang-Jeremy commented 1 year ago

Hi! Thank you for your assistance. This issue has been resolved.