Is there a way to identify trade events usign ETA C API
I'm using a ETA C API in Linux. I would like to know how to identify a trade event coming down in the feed. Is there an identifier in the API that I can use to identify such event ?
Since Reuters system performs trade safe conflation, how does Reuters system (ADH/ADS) identify trade events.
If there is no identifier available, what will be the recommended approach by Reuters to identify a trade ?
Best Answer
-
Hi @RAJ,
The recommended way to identify a trade is based on the fields that are included within the update. The API itself doesn't distinguish between the different types of market events such as quotes or trades. As an example, when an equity trade occurs, FID 6 (TRDPRC_1) which details the trade price along with FID 178 (TRDVOL_1) the number of shares will be included. When a quote comes in, these FIDs will not be included. However, different assets will carry the trade information within different FIDs. You will need to consult a content specialist if you need to understand trades for multiple asset types.
0
Answers
-
Does Reuters guarantee to include trade price and size irrespective of a value change if a trade event has taken place ?
For example, if the trade price and size stays the same between two trade events, does Reuters always pass through this data to the client application ?
Would you recommend us to look for only trade price or should we look for trade size as well ?
0 -
Hi @RAJ,
When a trade event occurs, all relevant FIDs will be included within that event irrespective of a value change. So if you receive 2 trades in a row with the exact same price and volume, you will be guaranteed to received these 2 fields. For trades, there are a number of other fields that will be included, some which will always change such as FID 32 (ACVOL_1) accumulated volume or FID 77 (NUM_MOVES) - the number of trades today.
I would recommend you simply look for the trade price field to determine that a trade occurs. I would also recommend you run a simple example, perhaps one of the simple ones included within the API or one of the tutorials within the developer portal. When running, monitor the output for the MarketPrice events and you can see the fields that come in and clearly see which ones will always be present. In addition, you can also contact a Thomson Reuters content specialist if you want to better understand which trade FIDs are appropriate for which asset types.
Hope this helps.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛