search

alvarobartt / investpy

Financial Data Extraction from Investing.com with Python
https://investpy.readthedocs.io/
MIT License
1.59k stars 375 forks source link

ERR#0015: error 503, try again later #364

Closed aktastunc closed 3 years ago

aktastunc commented 3 years ago

Hello,

I have been using same code for almost a year. But nowadays I am getting below error code:

"ERR#0015: error 503, try again later"

I tried simple examples from the documentation but couldn't get any result. If you can help me, I would be very pleased. I also attached a screenshot from the error of a simple code.

Screenshot
MaximilianSoerenPollak commented 3 years ago

Hey there, I have been developing with investpy recently too, and I started getting this error as well. Even after just one request through investpy.get_stocks_dividends() it already gives me this error. Maybe this is a new one?

caiovms commented 3 years ago

I believe there is something wrong indeed, I am getting the same error:

image

volantines commented 3 years ago

¿Investing API it's down?

https://www.investing.com/instruments/HistoricalDataAjax

image

LuccaPrado commented 3 years ago

Investing.com is really unstable/almost off the entire day today... It would be nice if we had some "caching" on the client side, as situations like that wouldn't be so frequent and impacting.

alvarobartt commented 3 years ago

Hi everyone @volantines, @LuccaPrado, @aktastunc, @caiovms, and @MaximilianSoeren :hugs:

As some of you say, Investing.com was experiencing some errors yesterday, but today it seems to be working fine! There's really nothing I can do with that as I'm not related to Investing.com at all so there's nothing I can do to solve this or cache the data as some of you suggested...

I'll include some functions to check the Investing.com API status so that you can check whether the error is on the client-side or on the server-side!

alvarobartt commented 3 years ago

BTW this has happened a few times during 2021, nothing too critical, as AFAIK Investing.com is updating the API, but I'm not aware of which changes, etc.

I'll be ready to keep investpy up to date so that it's as consistent as possible! :muscle:

LuccaPrado commented 3 years ago

Hi everyone @volantines, @LuccaPrado, @aktastunc, @caiovms, and @MaximilianSoeren :hugs:

As some of you say, Investing.com was experiencing some errors yesterday, but today it seems to be working fine! There's really nothing I can do with that as I'm not related to Investing.com at all so there's nothing I can do to solve this or cache the data as some of you suggested...

I'll include some functions to check the Investing.com API status so that you can check whether the error is on the client-side or on the server-side!

@alvarobartt what I said about caching is on client side, like, I get the funds information and the data is stored on my machine, so that, if the next call to the same endpoint fails, it can show the locally saved previous data with some anotation that It could be old.

alvarobartt commented 3 years ago

Sure @LuccaPrado, thanks for the proposal! Please from now on, track this issue in https://github.com/alvarobartt/investpy/issues/353 :hugs:

I'll get back to it once I complete the upcoming release!