Eikon API HTTP errors in previously working scripts

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

Find more posts tagged with

python

eikon

workspace

eikon-data-api

refinitiv-dataplatform-eikon

workspace-data-api

eikon-data-api-r

Accepted answers

Alex Putkov.1

@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.

All comments

Joris.Hoendervangers

Same here, need to investigate

Zhenya Kovalyov

eikonapir is not officially supported by Thomson Reuters, you can reach the creator directly at https://github.com/ahmedmohamedali/eikonapir

claudiu

this may be so but the package has not been changed since February and the scripts stopped working last week so the problem was caused by Thomson Reuters

Alex Putkov.1

claudiu

Thanks Alex. To summarize, the problem I saw was composed of 2 issues:

1. The problem described above with the get_symbology command in eikonapir.

2. An old app_id in the script. The eikonapir query commands used do not give a very informative error message and this combined with the problem described above caused my scripts to fail even after generating a new app id.

Update 27/6/2018: Issue 1 fixed in eikonapir package so problem solved. Since the error description (issue 2) has not been changed it will still throw the above described error for invalid app ids.

Joris.Hoendervangers

I've made a pull request on Github to remove 'set_app_id' from 'get_symbology'.

claudiu

great. checking for the app id error for all commands (get_timeseries, get_data...) and showing an error with the correct message would be an useful enhancement also.

mcasey

I've generated new APP ID and get the following message. Was working earlier and have never had this particular issue....

mc <- eikonapir::get_data("MSFT.O",'TR.CompanyMarketCap, SDate = 2019-10-01')

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

invalid 'digits' argument

EXPLORE OUR SITES