Different result between rdp API with workspace app and using config file.

Hi all,
We are currently building out an application that is using the Refinitiv RDP API to retrieve information. We have found two ways of connecting to the API :
- We can just open a session using rd.open_session(), when running code locally with the Refinitiv workspace open
- We can specify a config file containing our API key using rd.open_session(config_name='credentials.json') when running code for example in VMs in the cloud.
However I've noticed that I get different results from the exact same code when using those two methods.
From exemple, i'm running
df = rd.get_data(
universe = ['DE294876855=RRPS'],
fields = ['TR.FiMaturityBenchmarkRIC']
)
print(df)
To get the pricing benchmark of a specific bond.
Using rd.open_session() (or the codebook in WS), i get result :
Instrument Maturity Benchmark RIC 0 DE294876855=RRPS EU10YT=RR
Which is the expected result.
Running the exact same code with
rd.open_session(config_name='credentials.json')
from a VM, i get
RDError: Error code -1 | The access to field(s) denied. Requested universes: ['DE294876855=RRPS']. Requested fields: ['TR.FIMATURITYBENCHMARKRIC']
FYI the config.json file looks like this :
{
"logs": {
"level": "debug",
"transports": {
"console": {
"enabled": false
},
"file": {
"enabled": false,
"name": "refinitiv-data-lib.log"
}
}
},
"sessions": {
"default": "platform.rdp",
"platform": {
"rdp": {
"app-key": "APPKEY",
"username": "USERNAME",
"password": "PW"
},
"deployed": {
"app-key": "APPKEY",
"realtime-distribution-system": {
"url" : "URL",
"dacs" : {
"username" : "USERNAME",
"application-id" : APPID,
"position" : ""
}
}
}
},
"desktop": {
"workspace": {
"app-key": "APPKEY"
}
}
}
}
Has anyone encountered something like this ?
Thank you.
Adam LeRoux
Best Answer
-
Hello @adam.leroux
I checked the problem statement. Please confirm my understanding below:
- We can just open a session using rd.open_session(), when running code locally with the Refinitiv workspace open: This scenario uses a Desktop Session.
- We can specify a config file containing our API key using rd.open_session(config_name='credentials.json') when running code for example in VMs in the cloud.: This scenario uses a Platform Session.
If I am understanding the scenarios correctly. Please be informed that a Desktop Session connects and consumes data from the Workspace platform, while a Platform Session connects and consumes data from the Data Platform (or Delivery Platform, aka RDP). They are different platforms. The content sets, credentials, and permissions are not the same.
The permissioned you have on the Workspace platform/desktop application and the permissioned you have on the Data Platform are not the same.
If you need the same item permission on the Data Platform, please contact your LSEG Representative or Account Manager to help you with this permission issue. This permission issue cannot be fix via the code.
1
Answers
-
Hi thank you for the clarification.
I'll contact my rep.
Thank you, good day
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 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
- 249 ETA
- 554 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.9K Refinitiv Data Platform
- 643 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
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛