-
Notifications
You must be signed in to change notification settings - Fork 100
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
error response recieved from upstream api #26
Comments
Today it seems to be working again. |
I think Yahoo temporarily did something with their API. The yahooquery Python library also noticed issues: It was not working for about a day for me, but now it is working. |
This issue seems to be back, and has been going on for a few days. |
Perhaps reopen this bug. |
Changing the yahoo api url from |
I don't have permission to reopen the bug. |
Thanks @psanford, ran |
Guys, PR opened by @alai04 from last month fixed it for a while. However, about three days ago I've noticed that {"finance":{"result":null,"error":{"code":"Unauthorized","description":"Invalid Crumb. For Developers - https://bit.ly/yahoo-finance-api-feedback"}}} So after heading to the link, they basically say that they can't redistribute financial data from 3rd parties in API form. |
I switched to @psanford's fork and it seems to be working, at least for now: https://github.com/psanford/finance-go |
I also began seeing the Unauthorized errors again, even after switching to v1.1.0. Looks like the fork might be the way to go for now. |
Bumping this, as I received the same error on v1.1.0 when I run:
|
I'm getting
error response recieved from upstream api
on all requests. In the log, it says{"code":"Unauthorized","description":"Invalid Cookie"}
.The text was updated successfully, but these errors were encountered: