Using Elektron API seeing data as of 19th June for few Lipper RIC
Using Elektron API seeing data as of 19th June for few Lipper RIC
RICS:
LP40001481
LP40071600
LP60004185
LP60052825
LP65010917
LP65098435
LP65107123
LP68020134
LP68028847
LP68085367
LP68119589
LP68161769
LP68229471
LP68556142
field id :
11 21 6 22 25 19 32 16 12 13 118 0
Best Answer
-
Hi Zoya
Just heard back from Refinitiv support , this is actually a problem with Refinitiv upstream device cc2p-ddnbads06a since the same request with Lipper ric return correct data when we switch to the back up servers we have in place which point to a different Refinitiv upstream host cc1p-ddnbads04a
0
Answers
-
Attaching the request and response file tre10629.zip
0 -
Hello @debashish.bisoi,
You appear to be using Elektron API ( EMA? ETA? Websockets?) to consume Elektron realtime content?
If it's on realtime content, is your question that you do not see the updates from the instruments?
If correct, please test with the simplest consumer example included with your Elektron SDK (you do not state what language option you use) to verify that the issue is not specific to your custom app.
For sanity check, I just subscribed LP40001481 and the last update to TRADE_FAET field was on June 29th.
0 -
HI Zoya
it works fine for every other RIC , for eg /IBM.N gives me data as of today but only these RIC give data as of 19th JUne
0 -
Hello @debashish.bisoi,
In this case, my thinking is in a totally different direction. If when testing with a simple standard example, that came with your API SDK, for example, for EMA it's Example100_MarketPrice, (are you testing with a standard example or with a custom consumer app?) /IBM.N updates and LP40001481 does not,
Then the issue is likely not in the API, as with standard example testing, correct API usage is 100% assured.
And from the API usage standpoint consuming /IBM.N is exactly identical to consuming LP40001481 .
The issue is likely with permissioining for Lipper. /IBM.N is a delayed IBM, and is in many cases just permissioned as part of entitlements package, I suspect this may be true in your case. Lipper RICs are not available as "/" and have to be permissined separately.
Please contact your Refinitiv account manager, to confirm, that your user id is permissioned for Lipper content from Elektron.
0
Categories
- All Categories
- 6 AHS
- 39 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛