LSEG Data Library v2 authentication

Hello All,
I would like to ask you for advice, so one of my client recently receive RTO Service ID and he decide that he would like to use LSEG Data Library for Python in order to get data. He most likely use examples from our github page because in his application in order to authenticate he require "app-key", "username", "password" like below and this also lead me to conclusion that authentication method that he use is v1 which for RTO ServiceID is not the best option.
"sessions": {
"default": "platform.ldp",
"platform": {
"ldp": {
"app-key": "YOUR APP KEY GOES HERE!",
"username": "YOUR LDP LOGIN OR MACHINE GOES HERE!",
"password": "YOUR LDP PASSWORD GOES HERE!"
},
"deployed": {
"app-key": "YOUR APP KEY GOES HERE!",
"realtime-distribution-system": {
"url" : "YOUR DEPLOYED HOST:PORT GOES HERE!",
"dacs" : {
"username" : "YOUR DACS ID GOES HERE!",
"application-id" : 256,
"position" : ""
}
My question is: is it possible to that he can use v2 authentication method in LSEG Data Library (I have seen that this is possible but I could not find example of it) and if yes, is app-key still require? SO if it require still can I just generate it on this page
and it will be working with ServiceID?Answers
-
Hello @Kacper_Piernicki1
The v2 authentication can be used, but it is not defined in the configuration file. I was able to define and use it in the code as follows:
session = ld.session.platform.Definition( app_key = "NOT_NEEDED", grant = ld.session.platform.ClientCredentials( client_id="THE_CLIENT_ID", client_secret="THE_CLIENT_SECRET" ) ).get_session() session.open()
then requesting the real time data -
ld.session.set_default(session) response = ld.content.pricing.Definition( ['EUR=', 'GBP=', 'JPY=', 'CAD='], fields=['BID', 'ASK'] ).get_data() print(response.data.df)
0 -
Please try this one.
"platform": { "ldpv2": { "client_id": "<client_id>", "client_secret": "<client_secret>", "app-key": "<app_key>" },
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
- 685 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
- 252 ETA
- 556 WebSocket API
- 38 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
- 652 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
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 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 中文论坛