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

Which API keys should we use? #120

Open
jacobthill opened this issue Jan 24, 2025 · 0 comments
Open

Which API keys should we use? #120

jacobthill opened this issue Jan 24, 2025 · 0 comments
Assignees

Comments

@jacobthill
Copy link
Contributor

jacobthill commented Jan 24, 2025

See if we can associate API keys with a rialto list instead of a personal email.

Dimensions:
"With regards to a generic API account, the Dimensions Analytics API (which Stanford subscribes to) is always tied to an individual user account and there isn't really a way get around that. The accounts needs to have a working email address/account with Stanford as the key is only accessible after logging in via SSO. I'm not sure what application you are using Dimensions data for but we do have a CRIS API that is intended for populating Dimensions data into institutional systems."

OpenAlex:
"The API is the primary way to get OpenAlex data. It's free and requires no authentication. The daily limit for API calls is 100,000 requests per user per day. For best performance, add your email to all API requests, like" We can try to add our [email protected] email to get in the polite pool.

@jacobthill jacobthill self-assigned this Jan 24, 2025
@jacobthill jacobthill changed the title Verify API keys Which API keys should we use? Jan 29, 2025
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

1 participant