Using Elektron API seeing data as of 19th June for few Lipper RIC

debashish.bisoi

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

Find more posts tagged with

elektron

elektron-sdk

refinitiv-realtime

Accepted answers

debashish.bisoi

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

All comments

debashish.bisoi

Attaching the request and response file tre10629.zip

zoya faberov

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.

debashish.bisoi

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

zoya faberov

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.

debashish.bisoi

Hi Zoya

EXPLORE OUR SITES