How to use get_symbology method using Lipper ID
I tried to use the following call to search for different fund symbols. It was working using RIC, ISIN, but always got an error when using LipperID:
ek.get_symbology(["LP60000008"], from_symbol_type="RIC", to_symbol_type="LipperID")
It will fail using "from" or "to". I tried "lipperID", "LipperID", "Lipper ID", "Lipper_ID". I think the error message do not offer me a valid string for Lipper ID.
For the sample fund above the Lipper ID should be "60000008". i.e. the last 8 character in the RIC. It will be nice if a working sample using Lipper ID in get_symbology call can be provided.
Best Answer
-
The correct one should be "lipperID". However, in the request message, it has been changed to "LipperID". It could be the problem in the library.
('entity: ', 'SymbologySearch')
('payload: ', {'symbols': ['LP60000008'], 'to': ['LipperID'], 'from': 'RIC', 'bestMatchOnly': True})
Request: {"ID": "123", "Entity": {"E": "SymbologySearch", "W": {"symbols": ["LP60000008"], "to": ["LipperID"], "from": "RIC", "bestMatchOnly": true}}}
HTTP Response: 200 - {"ErrorCode":500,"ErrorMessage":"Can not process metadata for request: SymbologySearch.to - value doesn't fall in valid range: [RIC ISIN CUSIP SEDOL ticker lipperID OAPermID IMO]\n{\n \"bestMatchOnly\": true,\n \"from
\": \"RIC\",\n \"symbols\": [\n \"LP60000008\"\n ],\n \"to\": [\n \"LipperID\"\n ]\n}","Id":""}1
Answers
-
I got the following exception:
raise requests.HTTPError(error_message, response=server_response)
requests.exceptions.HTTPError: Can not process metadata for request: SymbologySe
arch.to - value doesn't fall in valid range: [RIC ISIN CUSIP SEDOL ticker lipper
ID OAPermID IMO]However, refer to Eikon Python API guide, the possible values for from_symbol_type and to_symbol_type are 'CUSIP', 'ISIN', 'SEDOL', 'RIC', and 'ticker'.
1 -
So the Error message showing "lipperID" is a valid option is a mistake and Lipper ID is not supported by this method? Hope someone can confirm that.
0 -
Great! So it is just a bug. Hope it can be fixed soon. Thank you for the quick response!
0 -
It sure looks like a bug in the Python library. I just tried the same request
get_symbology("LP60000008", from_symbol_type="RIC", to_symbol_type="lipperID"))
in R using eikonapir from GitHub, and it works just fine.1
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛