How to access the available FIDs given the CONTEXT_ID of a RIC ?
Depending on the RIC, a subset of the generally defined FIDs is present when subscribing using EMA C++ and the default channel dictionary.
I understand that the FID 5357 (CONTEXT_ID) can be somehow used to deduce the available FIDs.
How can this be done? Is there a way to do this programmatically using EMA C++ ?
Best Answer
-
If I understand your requirement correctly, Do you want to use EMA C++ to get a list of fields by using Context ID?
Basically, EMA and other TREP APIs can just pass only RIC name to the Provider or Elektron Data feed. The field list which available for each RIC depending on Data model used by the feed or service. API or consumer does not have capabilities to get the field list by using some specific field such as Context ID. It could say that the functionality you mentioned is not available in TREP APIs.
From my understanding of Context id, a broad definition is that it represents a specific set of FIDs and associated market logic for a given venue or feed. Context IDs are unique to a single Service and as such, they cannot exist in more than one Service. Essentially if you have a group of instruments that share the exact same characteristics from a single source then they can all share the same context id. In reality, you will get a different context id for different asset classes under the same source eg LSE Equities and LSE Bonds as well as against other sources eg BATS Europe Equities.
The Context Id is currently mastered in Data Model Discovery. EMA API does not have capabilities to access the information from the Data Model discovery tool.
I suggest you contact the Content Specialist team via Contact Us if you want to get more details about the Context ID.0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 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
- 248 ETA
- 552 WebSocket API
- 37 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
- 626 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛