SFC API vs Elektron SDK
Sorry if this post seems a bit confusing, but I inherited some legacy code that uses SFC to send and receive data. If I were to switch to Elektron SDK, is there a 1-to-1 mapping of the fields used in SFC to Elektron or are some fields no longer supported im Elektron?
Best Answer
-
The underlying data being represented by SFC is also represented by the Elektron SDK, they both source data from our IDN/Elektron real-time networks and the data dictionaries used have to be very similar in order to do this;
i.e. Subscribing to any RIC from the Elektron real-time feed using SFC, all the same fields will also be available through the Elektron API.
But there are some additional fields contained in the Elektron data dictionary that cannot be handled by SFC: This simply reflects the fact that the Elektron API's are capable of providing additional data models such as Market-by-price which are now available on our Elektron real-time feed.
Perhaps a more significant change for you will be the fact that SFC has Object representations for the data (Records,Services etc) the Elektron SDK consists of a Message API (EMA) and a low level Transport API.
0
Answers
-
Hi @daniel.roig
The list of fields you receive from the server is not dictated by the API - it is determined by the data source / server you connect to.
Assuming that you are consuming MarketFeed format data using SFC, the TREP infrastructure can convert a MarketFeed payload to an OMM FieldList - which you would consume using the Elektron SDK.
There maybe some subtle differences in the content of individual fields e.g. OMM data can represent blank fields - whereas MarketFeed can use "+0" to represent a blank price field for example.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 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
- 370 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 中文论坛