-
Notifications
You must be signed in to change notification settings - Fork 816
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
Adapt the HTTP calls to the latest changes in Google Trends API #570
Adapt the HTTP calls to the latest changes in Google Trends API #570
Conversation
Google Trends slightly changed its HTTP requests calls: - the "get cookie" request changed its URL, needed now an extra "explore/"; this was the main reason of the premature 429 error responses. - the "widgets" request is now POST instead of GET. Before this change the requests returned almost consistently 429 error responses, now it returns results again. Fixes GeneralMills#566, GeneralMills#567, GeneralMills#561
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do the following changes.
Hey there,
Why did you add this change in addition to the first one ? |
Hi @Michae94, Because that's how the Google Trends website behaves, I guess the most secure way to prevent to be blocked is to mimic the website. |
Hi @Terseus , thanks for sharing this solution. |
Hi @DamianDavid, I don't recommend you using the Try to adhere to this workflow:
If in doubt on how to use a specific method, take a look at the tests. |
Hey all, is there an ETA on this? As the trends function has been broken for a few weeks and it seems this is the only solution going in? |
Hi any update on merging this? |
Is this resolved? |
Google Trends slightly changed its HTTP requests calls:
Before this change the requests returned almost consistently 429 error responses, now it returns results again.
Fixes #566, #567, #561