Eikon API HTTP errors in previously working scripts

claudiu
claudiu Explorer
in Eikon Data APIs

I can't get my Eikon API scripts to work anymore. I created a new App Key to check if this is the problem but this didn't help. Example of command and error message:

> get_timeseries("MSFT.O","*","2016-01-01T15:04:05","2016-01-10T15:04:05","daily")

Error in print.default("HTTP Error, code= ", response$status_code, sep = "") :
invalid 'digits' argument

I use the eikonapir package for interfacing with R.

Was there something done at the server side? (I received a message from Reuters that Eikon Data API is getting out of beta into production)

Thanks,

claudiu

Tagged:

Best Answer

  • Alex Putkov.1
    Alex Putkov.1 ✭✭✭✭✭
    Answer ✓

    @claudiu
    Thank you for providing the details that helped me reproduce and analyze the issue.
    The root cause of the problem is a deficiency in eikonapir package, specifically in the implementation of get_symbology method. If you look at the source code on GitHub you'll see that the function starts with calling set_app_id method and setting the app key to a hardcoded value. This was of no significance while TR did not validate the app IDs. Since last weekend TR started validating app keys and that's when the deficiency in eikonapir package became apparent and critical. Every time you call get_symbology method the method sets the app key to an invalid value and any data retrieval method you execute subsequently fails unless you call set_app_id method in your script and reset the app key to a valid value. But the next time you call get_symbology method, not only will the method fail, but it will also reset the app key to an invalid value and all subsequent data retrieval calls will fail again.
    As an immediate workaround I can suggest replacing get_symbology calls with get_data for symbology conversion, e.g. get_data("MSFT.O","TR.ISIN").
    Eikonapir is an open source project. Everyone is welcome to contribute a bug fix.

Answers

Categories