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

PubChem needs API key support #59

Open
egonw opened this issue Nov 2, 2017 · 3 comments
Open

PubChem needs API key support #59

egonw opened this issue Nov 2, 2017 · 3 comments

Comments

@egonw
Copy link
Member

egonw commented Nov 2, 2017

From their blog [0]:

I author software that accesses the E-utilities, and this software is used
by other people. Do those users need keys?

Yes, but only if your software allows them to post more than
3 requests/second. For such cases, we recommend that you allow users
to enter their own API key as a setting in the software.  Please 
contact us if you have questions or for more information on this approach.

@jonalv, can you help me with the user account support?

0.https://ncbiinsights.ncbi.nlm.nih.gov/2017/11/02/new-api-keys-for-the-e-utilities/?campaign=twitter-11022017

@egonw
Copy link
Member Author

egonw commented Nov 2, 2017

Note to self: introduce a 0.3s time out in the call if the user does not use a API key.

@jonalv
Copy link
Member

jonalv commented Nov 16, 2017

What do you need help with more exactly? Sadly I don't really remember how this stuff worked...

@egonw egonw closed this as completed Nov 16, 2017
@egonw egonw reopened this Nov 16, 2017
@egonw egonw unassigned egonw and jonalv Apr 29, 2018
@egonw
Copy link
Member Author

egonw commented Apr 29, 2018

OK, long term.

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

No branches or pull requests

2 participants