Clarification on Differences Between eikon and refinitiv-data Libraries

I have a question regarding the appropriate usage of the eikon and refinitiv-data Python libraries for retrieving company metadata based on RICs.
Previously, I have used the eikon package as follows to retrieve metadata fields such as "TR.RIC", "TR.ExchangeName", "TR.ExchangeTicker", "CURRENCY", "TR.ISIN", and "TR.CUSIP":
import eikon as ek
ek.set_app_key("...")
df, err = ek.get_data(ric_list, fields)
However, I have recently tested the newer refinitiv-data package and found that the following also returns valid metadata for the same RICs:
import refinitiv.data as rd
rd.open_session()
df = rd.get_data(universe=ric_list, fields=fields)
Could you please clarify:
If I use the same RICs and fields, will the data returned by the eikon library and the refinitiv.data library be exactly the same?
Best Answer
-
The API call can use almost every identifier except tickers. You can use RIC, ISIN, CUSIP or PERM_ID etc with the get_data API calls.
0
Answers
-
Hello @Ziye
Most of the code using the legacy EDAPI will work with the new data libraries with minimal change. Please refer to this article to understand and use the Data library migration steps.
Also note that you should migrate to the newer LD Library, which works quite similarly. Here are the code samples for it.
2 -
Dear Gurpreet,
Thanks for your respone.
May I also ask what can be used in the universe parameter of the ld.get_data() function? I understand that RICs are commonly used, but I would like to know whether other identifiers such as ISINs, CUSIPs, SEDOLs, PermIDs, or OrgIDs are also valid inputs. I reviewed the documentation in the GitHub repository lseg-api-examples, but the only detail provided under universe is: "Single instrument or list of instruments to request."
0 -
The API call expects the RIC. Other instruments like ISIN, Tickets etc can be converted to RIC's first as described in this discussion.
0 -
Got it — RICs are the default expected identifiers for the get_data() function.
However, in my testing, I’ve been able to successfully retrieve correct results using PermIDs in the universe parameter.
Just to clarify, is this officially supported by LSEG? Looking forward to hearing from you.
0 -
As far as I know, the function supports PermIDs.
It uses the same backend as the @RDP .Data function in LSEG Workspace Excel.
To confirm whether the @RDP .Data function supports PermIDs, you may need to contact the product team through LSEG Support.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 704 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 2.9K Elektron
- 1.5K EMA
- 257 ETA
- 566 WebSocket API
- 40 FX Venues
- 16 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.1K Refinitiv Data Platform
- 842 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 195 TREP Infrastructure
- 232 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 101 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛