How to avoid HTTP status 429 (too many requests)?

[Rombersoft]

Who can share experiences about problems with HttpStatus 429 (Too many requests)? I noticed that the developer thought about using the proxy server. Does it exist some statistics about what I must do in order to be banned by Google Corporation? Public API is missing and how much is legal to use google back end in order to show google trends results on my own site???

[Hibrix-net]

Hi,

I've never counted how many request you can perform before being blocked, but yes there's some kind of limit for that and there's nothing you can do to avoid the temporary banning apart from the use of proxies. I believe it is a combination of num. of request in a particular timeframe what produces the 429's.

I don't think there's any legal restriction for using their unofficial endpoints, you just will encounter the blockages and that's about it.

Sorry to don't be more helpful. Kind regards,

[Hibrix-net]

I believe the too many requests error is done by the Google API limitations, so nothing that can be really "fixed" by code other than using proxies.

Are we talking about 2 different things here? Am I missing something?

Best,

[Mustafa-Ellebody]

I tried many solutions, but this one doesn't seem to get blocked: https://rapidapi.com/odlica-odlica-default/api/trendly

[rithvikshetty]

@Mustafa-Ellebody Is this still reliable and How is the performance? Does it go down frequently?

[Mustafa-Ellebody]

@rithvikshetty Yes It's still reliable and scalable to 100ks of requests/month. It's service level is 100% so now down times so far.

[mahdikhojasteh]

@Mustafa-Ellebody I subscribed for https://rapidapi.com/odlica-odlica-default/api/trendly and for related queries and related topics it returns ( regardless of any input, even with its sample input values ): { "msg": "No results found!" }

I don't call this reliable. There is also no support for this.

FYI @rithvikshetty

[Odlica-Corp]

Thanks @mahdikhojasteh for pointing out to this issue. The issue you described didn't happen often so it was unnoticed from our side. We worked on this issue and it should be solved now. Please try again and reach out if you face any issues. @rithvikshetty We will also be very happy to hear your feedback.