Urgent request for an R library compatible with Refinitiv Workspace

mcomisso · 2025-04-11T14:51:24+00:00

There was an error rendering this rich post.

We are currently using the R package eikonapir to access the Eikon Data API. However, this API is not compatible with Refinitiv Workspace, which is now our main platform.

Due to an upcoming migration deadline, we urgently need an R-compatible alternative that offers the same data access and functionalities, but works with Refinitiv Workspace.

We would appreciate any official library or recommended method to continue our integration in R.

Thank you.

Find more posts tagged with

refinitiv-dataplatform-eikon

r-studio

#technology

#product

Workspace API

r package

r package for Workspace

Accepted answers

All comments

Jirapongse

@mcomisso

Thank you for reaching out to us.

As far as I know, eikonapir should be able to run with Workspace as long as the connected TCP port is correct.

set_proxy_port(9000L)

Currently, we don't have any official libraries for R.

mcomisso

Hi, thank you for your response.

I tried running the eikonapir package and set the TCP port using set_proxy_port(9000L) as suggested. However, when I attempt a simple data request like:

ggal_book <- eikonapir::get_data(  instruments = "GGAL.O",  fields = list("BID", "ASK"))

I receive the following error:

Error in curl::curl_fetch_memory(url, handle = handle) :   Failed to connect to localhost port 9000 after 2249 ms: Couldn't connect to server

This seems to indicate that there is no service running on localhost:9000. From what I understand, this port was previously used by the Eikon Data API Proxy, but I believe Refinitiv Workspace no longer includes or starts this proxy by default.

Could you please confirm whether Workspace still supports this kind of connection with eikonapir?
Is there a way to enable the proxy in the current setup, or should I migrate to the new refinitiv-data library in Python?

Thanks again, looking forward to your guidance.

Jirapongse

@mcomisso

My eikonapir works with Workspace.

You may check the TCP port from the About LSEG Workspace page.

The port is on the Data API proxy page.

Yes, it is better to migrate the application to use the LSEG Data Library for Python instead. The examples and tutorials are on GitHub.

EXPLORE OUR SITES