Adapt the HTTP calls to the latest changes in Google Trends API

[Terseus]

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 #566, #567, #561

[akash-ai]

Please do the following changes.

[Michae94]

Hey there,

• the "widgets" request is now POST instead of GET.

Why did you add this change in addition to the first one ?

[Terseus]

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.

[DamianDavid]

Hi @Terseus , thanks for sharing this solution.
I applied the 'get cookie' step and It works fine when I run the codes from Jupyter, but it still shows the error message when running from https://datalore.jetbrains.com/ which is a web platform I use to schedule scripts. Could it be because I still need to execute the step two 'widgets'?

[Terseus]

Hi @DamianDavid,

I don't recommend you using the GetGoogleCookie outside of the TrendReq class.

Try to adhere to this workflow:

• create a new TrendReq object.
• call build_payload.
• call the method needed to obtain the information you want (e.g. interest_over_time).

If in doubt on how to use a specific method, take a look at the tests.

[datacubed]

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?

[josh-ashkinaze]

Hi any update on merging this?

[jabeztadesse]

Is this resolved?