Hi @HeikoRR, related to my previous answer, it looks you are using my fork of the R api. It also looks like from the answer of @zoya.farberov that the python api returns the same results, so it is not an R api related issue.

Hello @HeikoRR,

Can try:

rics = ["BV","SI","VIR.O"]
ek.get_symbology(rics, from_symbol_type="RIC", to_symbol_type="ISIN", bestMatch=False)

Should see:

Does this help?

Thank you Zoya.

My setup is in "R": I changed the bestMatch to False. The output has the correct ISINs but also add other unrelated ISINs - not very useful output. The first respective ISIN is correct but why the others ones - seems every time I am trying to accomplish the simplest tasks on the API there are these kinds of errors/outputs. Never had any of these issues with Bloomberg API.

> get_symbology(list("BV","SI","VIR.O"), from_symbol_type="RIC", to_symbol_type="ISIN",bestMatch=FALSE)

OUTPUT:

Symbol error ISIN

1 BV No best match available <NA>

2 SI No best match available <NA>

3 VIR.O <NA> US92764N1028

ISINs

1 US10948C1071, CA04016J1021

2 US82837P4081, CA89131L1085, US8261975010, ARDEUT112372, GB00H1WSCJ50, GB00H1WVC720, GB00H1WS6B52, GB00H1WV6149, GB00H1WSCK65, GB00H1WS6C69, GB00H1WVC837, GB00H1WV6255, GB00H1WTZM24, GB00H1WVK673, GB00H1WVCY98, GB00H1WSD708, GB00H1WVK780, GB00H1WV6362, GB00H1WSD815, GB00H1WSCL72, GB00H1WTZN31, GB00H1WVCZ06, GB00H1WS6D76, GB00H1WVC944, GB00H1WV4656, GB00H1WVPT58, GB00H1WVPS42, GB00H1WV4540, GB00H1WVHG61, GB00H1WTXW81, GB00H1WTXV74, GB00H1WVHF54, GB00H1WTZL17, GB00H1WVPR35, GB00H1WVCX81, GB00H1WTXT52, GB00H1WVK566, GB00H1WV4433, GB00H1WSD690, GB00H1WVHD31, GB00H1WSBP46, GB00H1WVBD11, GB00H1WVBF35, GB00H1WSBQ52, GB00H1WVNF72, GB00H1WV2T43, GB00H1WVND58, GB00H1WV2S36, GB00H1WV4326, GB00H1WVK459, GB00H1WSD583, GB00H1WVBC04, GB00H1WV6032, GB00H1WVHC24, GB00H1WV2R29, GB00H1WVNC42, GB00H1WSCH37, GB00H1WTZK00, GB00H1WTXS46, GB00H1WVCW74, GB00H1WVC613, GB00H1WS6938, GB00H1WVPQ28, GB00H1WSBN22, GB00H1WTYC50, GB00H1WVHY44, GB00H1WS6821, GB00H1WVPP11, GB00H1WSBM15, GB00H1WVC506, GB00H1WTXR39, GB00H1WVHX37, GB00H1WVNB35, GB00H1WTZJ94, GB00H1WVCV67, GB00H1WV5Z18, GB00H1WVHB17, GB00H1WV2Q12, GB00H1WSCG20, GB00H1WVBB96, GB00H1WSD476, GB00H1WV4219, GB00H1WVK343, GB00H1WTYB44, GB00H1WSD369, GB00H1WVB979, GB00H1WV4102, GB00H1WVK236, GB00H1WTY926, GB00H1WSCF13, GB00H1WV2P05, GB00H1WVH992, GB00H1WV5Y01, GB00H1WVCT46, GB00H1WTZH70, GB00H1WTXQ22

3

Hello @HeikoRR,

I am sorry to hear you find integration to be less then smooth sailing.

Please note that EikonAPIR does not have to be identical to Eikon Data API Python in all aspects, as it is not developed by Refinitiv. It is offered via EikonAPIR on GitHub by a separate provider.

Took a look at get_data.Rd and do not see any mention of bestMatch parameter exposed via R. From the difference in output, either it is not exposed or the correct usage differs.

I would suggest asking the provider of the API if bestMatch parameter is exposed by EikonAPIR, to be certain of the usage?

Hi @HeikoRR, I guess that the version of the api you are using does not support the bestMatch argument. I have a fork of the github repository with bestMatch support that you could try: https://github.com/philaris/eikonapir.