Yahoo Finance: too many requests / Getting errors on updates (desktop only)

Das hab ich auf stackoverflow gefunden:

https://stackoverflow.com/questions/78111453/yahoo-finance-api-file-get-contents-429-too-many-requests

Da wird ein user-agent im header übergeben…

thank you very much for your commitment!
Unfortunately, the problem still exists when you want to add a new security :confused:

To add a new instrument, you can use the “empty instrument” option.

@jkk1 this issue is already reported:

1 Like

Die beschriebene Geschichte bei stackoverflow ist ja auch schon mehr als ein Jahr alt, und außerdem https://stackoverflow.com/questions/78111453/yahoo-finance-api-file-get-contents-429-too-many-requests#comment140118397_78111952

1 Like

Awesome! Thanks for the quick action, works like a charm. :+1:

When you have time, could you please consider helping users on older version (0.71.x) with old MacOS like myself? Thank you!

2 Likes

Should be available now via online update or download.

3 Likes

Many many thanks for your prompt assistance - it’s now working perfectly well on the older version !

It works now!! Thanks.

Still the same Error allthough I updated to the newest version :confused:

Are you sure you did, you would be the first one, or Yahoo would have done another change in the meanwhile.

Can you please double-check!

1 Like

Version: 0.76.1 (Mai 2025)

Platform: win32, x86_64

Java: 21.0.5+11-LTS, Azul Systems, Inc.

I can add new stocks but it always shows this error:

This was covered earlier in the thread. You might need to add an empty instrument and then configure it for Yahoo.

1 Like

For those using Arch Linux the package maintainer has just put an update in the AUR. And it works. Many thanks.

1 Like

Yes it fixes native yahoo finance request. However if one uses yahoo requests over JSON provider, the same issue persist. Could you add randomization of user agent to the JSON provider too?

Why should you do that?

Because Yahoo returns GBX but imported buy orders are in GBP, so I need to convert quoted values. And one can only do that with usage of custom JSON provider.

OK, now it makes sense.

There is a fix in the Yahoo provider that should adopt this. Use of JSON should not be needed for JSON Yahoo Finance anymore.