I got some error message when I use get_data() function.

I need all option data for specific underlying asset.
For example, when I use below code,
rd.get_data("0#SPX*.U", fields =['TR.BIDPRICE'])
then I got
Error code -1 | Unable to resolve all requested identifiers in ['0#SPX*.U'].
And I have another question about that function.
I can get some fields which have 'TR' in the field name (TR.RIC for example),
but I can check another fields without 'TR'(DSPLY_NAME for example) in the refinitiv workspace but can't get data with python api.
For example, when I use
rd.get_data('KS200305H3.KS',['TR.THETA','THETA','CF_NAME'])
the It just returns belows(It doesn't return 'THETA' and 'CF_NAME' but only 'TR.THETA')
Instrument Theta
0 KS200305H3.KS -0.031415
I don't know what's the problem with them.
Please get me some information about them.
thanks.
Best Answer
-
Thank you for reaching out to us.
I tested the code with the desktop.workspace session.
The error indicates that the API is unable to resolve this chain RIC: 0#SPX*.U.
You may try to use the EX-1.01.07-Chains example. This example will resolve a chain RIC by using the real-time feed then it will use the retrieved RICs with the get_data method to retrieve data. However, to use this example, you must have permission to access the Real-Time data of this chain RIC (0#SPX.U).
Regarding the second problem, you may need to enable logging in the API by adding the following configuration in the RD configuration file (refinitiv-data.config.json).
{
"logs": {
"level": "debug",
"transports": {
"console": {
"enabled": false
},
"file": {
"enabled": true,
"name": "refinitiv-data-lib.log"
}
}
},
"sessions": {
"default": "desktop.workspace",
...
...THETA and CF_NAME are real-time fields. You may not have permission to access the real-time of this RIC.
on_complete_stream_event ({'ID': 5, 'Type': 'Status', 'Key': {'Service': 'IDN_FD3', 'Name': 'KS200305H3.KS'}, 'State': {'Stream': 'Closed', 'Data': 'Suspect', 'Code': 'NotEntitled', 'Text': 'Access Denied: User req to PE(6504)'}},)
Otherwise, if you are using the desktop session, you may use Eikon Data API in the RD library instead.
import refinitiv.data.eikon as ek
ek.set_app_key('<app key>')
df, err = ek.get_data('KS200305H3.KS',['TR.THETA','THETA','CF_NAME'])
df0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 625 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛