Welcome to the LSEG Developer Community
I was hoping a developer could answer the below questions for a client on RFA: We are currently using the RFA C++ SDK to subscribe to L1 and L2 information via the MarketPrice domain (using derived RICs via regex pattern matching). For better maintainability and ease of onboarding new symbols / exchanges, we wanted to find…
will their legacy APIs still work after a planned upgrade from LSEG side ?(PCN206364)
Hi, Do we have a list of error messages returning from RTO and its explanation…example like F2:Not in Cache
Hi Team, can you tell from this whether the code we currently maintain is compatible with the proposed connectivity by out client? api "com.reuters:rfa:8.0.0.E2", "com.reuters:config_loader:8.0.0.E2"implementation "com.refinitiv.ema:ema:3.6.3.0", "com.refinitiv.eta:eta:3.6.3.0",…
is there a way to subscribe to all the RIC chains (and subsequently the underlying RICs) under that PE code. I’m assuming it would be things beginning with a 0# (e.g. 0#UNBK:NS). I was curious if there was a programmatic way we could do so rather than sifting through the PE's 9840 pages. Or if there is a particular keyword…
We could get SONIAOSR= by TREP last week but I can't get it from this week. I think this is caused by below PDP change and I added the entitlement of new PDP to our account. WWERTNEASP ⇒ WWOTCNTR But I still can't get it. Is there any change for SONIAOSR= ?
Customers must migrate to strategic APIs by 28 February. However, RTMDS will continue to support Marketfeed and SSL until Q2 2027, so the unsupported legacy APIs will continue to work until then. Why they MUST migrate by 28 Feb if it'll will work up to Q2 2027?
Having issue SFC C++ API where L2 market data of TU contract is impacted, please investigate Asap
It looks like you're new here. Sign in or register to get started.
