Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No working way to get API keys #33

Open
Nosferican opened this issue Dec 13, 2016 · 1 comment
Open

No working way to get API keys #33

Nosferican opened this issue Dec 13, 2016 · 1 comment

Comments

@Nosferican
Copy link

The link for filling out the form to get a key for the API is not working. It yields services.sunlightlabs.com’s server DNS address could not be found. I am aware it is not directly a python-sunlight issue, but it affects it nonetheless. Not sure where exactly to bring the issue.

@jonathanng
Copy link

Sunlight Congress API: The API is currently running at its original address and supports all of the calls it did before the move. What’s missing right now is the ability to sign up for an API key, so we’ve turned off the requirement to have one for the moment. If you are an existing API user, don’t change anything. If you are a new user, you can use the API right now without a key, but we will require keys once we have a solution in place. We will be moving the API to a propublica.org address, but none of the other parts of the URL will change, and we do not anticipate removing any existing responses.

Much of the legislative data that powers the API comes from the United States project. We’ll be contributing to the efforts there and we invite users of the API to get involved, too, by contributing code for new or existing sources of information, or by updating information about members of Congress.

ProPublica has its own Congress API (which started life as The New York Times Congress API), but Sunlight’s is more robust and has many more users, so our plan is to merge the ProPublica Congress API into the Sunlight API to that we can offer a single service. The process will begin this month and continue into early 2017. Once we’ve completed that transition we’ll have a single Congress API. If you are interested in helping us test things out during the transition, email us at [email protected].

Source

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants