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.

Sign up for GitHub

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

Jump to bottom

Passing API keys #39

Closed
carmelotony opened this issue Jan 5, 2021 · 3 comments
Closed

Passing API keys #39

carmelotony opened this issue Jan 5, 2021 · 3 comments
Labels
future release will be included in a future release help wanted

Comments

@carmelotony
Copy link

Is there a way to pass CryptoCompare API keys to pull down more data?
@lagerfeuer
Copy link
Owner

Sorry for the late response. No, there is no way to do that currently. I've had it on my radar for a while, but since I don't really use this library anymore, I haven't had the need to update it. Feel free to open a pull request if you have the time, I'd gladly merge it.

@lagerfeuer lagerfeuer added future release will be included in a future release help wanted labels Jan 17, 2021
@carmelotony
Copy link
Author

No Worries. Thanks for setting this up. I was able to pull the historic data I need over a few days. If I end up using higher frequency data, I'll look into adding a paid API key. Thanks again, this was really useful.

@PatrickAlphaC PatrickAlphaC mentioned this issue Jan 23, 2021
Merged
@lagerfeuer
Copy link
Owner

@carmelotony This was addressed in #40, take a look if that's what you need! Going to release it later today. Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
future release will be included in a future release help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lagerfeuer @carmelotony