-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
solution for investiny 403 #54
Comments
to make reliable solution we need to switch between multi api |
tvc6 is working fine they banned tvc4 |
Thanks, @ramakrishnamekala129 already been fixed, and released, it's available at https://github.com/alvarobartt/investiny/releases/tag/v0.7.2, should be installable in some minutes with |
@ramakrishnamekala129 I know that you already shared this URL with me in the past, but where did you get that URL from? Just by randomly testing different |
FYI after some testing, it seems that |
Since investpy stopped working my main stopped working so I started searching backdoor in investing.com so I got tvc4 in Indian site after so made request methods which worked fine for 3 to4 days after that I sent so that repair investpy along with that after searching countries investing.com then I got tvc6 Australia which had some sharing between American investing so concluded that they work differently. |
Hey guys, I'm using the investpy 7.2.0 but I got the same preview error: 403. Any clue to how deal with this problem? |
Let me check this again later, as it shouldn't happen any more as far as I could test... Can you try with |
Ok already tested it @Emmanuel1524 aaaaand... bad news, all the Investing.com APIs seem to be Cloudflare protected now... let me check for alternative solutions as proposed at #56 😞 |
please use which is working api
import requests
from requests.structures import CaseInsensitiveDict
while True:
i=['1138417','17955','101810','160',]
for k in i:
url = f"https://tvc6.investing.com/9368e857cc51ddcae69108bd8a3b6d49/1664515691/56/56/23/history?symbol={k}&resolution=D&from=1633411692&to=1664515752"
The text was updated successfully, but these errors were encountered: