How do I determine the RIC name of Market By Price information with an equity RIC name given
Given an equity RIC, e.g. 8411.T, 0001.HK, how should my logic determine the RIC name for the respective market by price information?
Is there a table of exchanges which indicates adding "D" as prefix or adding "d" as suffix to the main RIC to get the level 2 RIC?
But that would be a static table.
Should I refer one of the FIDs from prefix "0#" to get the name of the level 2 RIC? Like "LONGLINK2" for 0#8411.T? But seems like the FID that carries the level 2 RIC name are not consistent across other exchanges.
Best Answer
-
Hi @otto.to
If you want the full market by price order book, just change the Domain in the Req from MarketPrice to MarketByPrice.
The exact Enum you will have to use may vary slightly depending on which API you are using e.g.
if you are using EMA Java it would be something like:
EmaFactory.createReqMsg().domainType(EmaRdm.MMT_MARKET_BY_PRICE) .serviceName("DIRECT_FEED").name("AAO.V"), appClient, 0)
for EMA C++ it would be something like:
consumer.registerClient( ReqMsg().domainType( MMT_MARKET_BY_PRICE ).serviceName( "DIRECT_FEED" ).name( "AAO.V" ), client );
Please refer to EMA Consumer example 140 which is included with both EMA Java and C++ - which request MarketByOrder rather than MarketbyPrice - but the principle is the same.
You may also find the intro part of the following article useful.
How to Sort & Process Level 2 Orderbook Data using EMA C++ API | Refinitiv Developers
You should also reference the RDMUsageGuide.pdf which is provided with both of the above SDKs - for details on the definition and structure of the MarketByPrice domain.
Having said all of the above, if you are only interested in top of order book and / or data in a standard MarketPrice instrument, then I recommend you contact the Content Helpdesk at My.Refinitiv who should be able to advise on the exact RICs you require.
0
Answers
-
Thanks. I think this should work.
But how about legacy level 2?
0 -
When I briefly worked with legacy MarketPrice format Level 2 data, I found the RIC naming rules varied somewhat and I had to rely on the Content Helpdesk to provide the naming convention.
I just corrected my final paragraph above to indicate MarketPrice - sorry.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
- 651 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 中文论坛