Bill Actions endpoint reaching status 500 errors

[edward-coretsu]

There's a fair number of bills actions endpoint calls that results in a 500 error with

"error": "The QuerySet value for an exact lookup must be limited to one result using slicing. (ValueError)",

some examples:
https://api.congress.gov/v3/bill/17/s/1/actions?format=json&limit=250&offset=0
https://api.congress.gov/v3/bill/16/s/11/actions?format=json&limit=250&offset=0
https://api.congress.gov/v3/bill/16/s/68/actions?format=json&limit=250&offset=0
https://api.congress.gov/v3/bill/20/s/45/actions?format=json&limit=250&offset=0

[apreiter18]

Thank you for reporting this, @edward-coretsu - I am going to need some time to investigate this further. In earlier Congresses, such as those of the late 18th and early 19th centuries, there will be instances where bill numbering is not clear or evident. At this point in time, Congressional staff had not yet standardized how bills get numbered. Thus, there are instances where two legitimate bills have been assigned the same number. To make a distinction between the first session-introduced bill and the second session-introduced bill we add the “introduction date” to the URLs for these bills on Congress.gov. However, this distinction is not evident when returning data within the Congress.gov API's bill action endpoint.

I'll try to troubleshoot and use this Git issue as a hub for any relevant updates. Stay tuned!

[remolloy1010]

any updates on this issue?

[apreiter18]

@remolloy1010 - No, I don't have an update yet.