api.congress.gov icon indicating copy to clipboard operation
api.congress.gov copied to clipboard

API key not working

Open CubicleJockey opened this issue 3 weeks ago • 4 comments
trafficstars

I recently went through the Congress.gov API signup process and received an API via the page after sign-up and well as in the email I signed up with. It did not work within the swagger at Swagger. I gave it a few days and I am still getting authentication denied using the given API key. Can I please get assistance?

CubicleJockey avatar Oct 27 '25 03:10 CubicleJockey

Looks like this is a bug with the test utility. Didn't realize this before, but the domain of the API docs is gpo.congress.gov, whereas the actual API is hosted at api.congress.gov. Just tried it myself and got the same result, but api.congress.gov works as expected.

Gmanicus avatar Oct 29 '25 01:10 Gmanicus

Yep. That was it I am able to successfully make calls now. Thank you for that.

On a side note. What is the best way to go about making a request? Is it still the issues section?

It would be nice if the Swagger Schema section was setup so we can see the samples of request and response objects.

Thanks again for the help.

CubicleJockey avatar Oct 29 '25 03:10 CubicleJockey

You're very welcome.

What is the best way to go about making a request? Is it still the issues section?

Yes, it is. Normally, the team will get back to you within a day or two, but I believe they as well as the rest of the Library of Congress have been affected by the shutdown and will be out of office for the time being. :(

Gmanicus avatar Oct 29 '25 05:10 Gmanicus

Library of Congress have been affected by the shutdown and will be out of office for the time being. :(

Best of wishes to all that are affected.

CubicleJockey avatar Oct 29 '25 14:10 CubicleJockey

@CubicleJockey - I just reviewed your link again and noticed it is directing to gpo.congress.gov. The correct URL for API requests is api.congress.gov.

I noticed that the Google results are showing gpo.congress.gov again. We had resolved that but it apparently resumed at some point. I will work on addressing that. Thank you!

apreiter18 avatar Nov 13 '25 21:11 apreiter18