Failed to obtain crumb – Repeated 429 errors limit data retrieval

[E-Asrar-Haghighi]

Hi team,

I'm encountering a recurring issue when attempting to retrieve data. The process fails with the following message:

Failed to obtain crumb. Ability to retrieve data will be significantly limited.
---------------------------------------------------------------------------
ResponseError                             Traceback (most recent call last)
ResponseError: too many 429 error responses

The above exception was the direct cause of the following exception:
.
.
.
.
.

RetryError: HTTPSConnectionPool(host='query2.finance.yahoo.com', port=443): Max retries exceeded with url: /v10/finance/quoteSummary/AAPL?modules=financialData&formatted=false&lang=en-US&region=US&corsDomain=finance.yahoo.com (Caused by ResponseError('too many 429 error responses'))

It seems like the server is rate-limiting the requests (HTTP 429: Too Many Requests). This is significantly impacting functionality.

The strange thing is that this exact code was working perfectly just a few days ago without any errors. I haven't changed anything on my side.

Has anyone else faced this issue? Is there a recommended fix or workaround ?

Thanks in advance!

[tjean00]

Same here. There is a long discussion on yfinance and possibly a fix coming from there.

[E-Asrar-Haghighi]

Hope we're coming up with a solution, I like this library, and I wrote a lot of code using it

[tjean00]

Looks like a similar solution as the one uncovered on yfinance is working here. The following seems to work for me:

import yahooquery as yq

from curl_cffi import requests
session = requests.Session(impersonate="chrome")

t = yq.Ticker("AAPL", session=session)
print( "regular market price:", tq.price["AAPL"]['regularMarketPrice'])
h=tq.history(period="1wk")

[E-Asrar-Haghighi]

Thank you very much! It works perfectly for me.

[james-stevens]

I started getting this issue a lot starting today, querying from the UK - this workaround also appears to fix the issue.

thanks 👍

[maread99]

Thanks for posting the workaround @tjean00!

For reference, this discussion has been raised as issue #315.