Best practice news feed (polling)
Hi all,
I was wondering what would be the best practice regarding news feed polling in order to react to certain news events. Would it be fine to call the get_news_headlines function every few seconds and the backend in the worst case will limit the requests or what would be the max limit that you recommend?
Do you have some kind of subscribe to Instrument/News ticker function on your to-do list in order that the server keeps pushing new data instead of the client requesting them?
Thanks,
Best regards,
Philipp
Best Answer
-
I should add to Gurpreet's response that capability to retrieve streaming market data is on the roadmap for Eikon Data API. It is expected to be delivered this year. The capability to subscribe to streaming news headlines with filters however is not currently on the roadmap. It's very likely that using streaming market data capability you will be able to subscribe to RIC NFCP_UBMS, which provides streaming news headlines without any filtering. The filtering you would then need to implement yourself based on the payload of news headlines updates. Eikon COM and .NET APIs can be used to subscribe to NFCP_UBMS today.
In Eikon Data API executing get_news_headlines method is the only option to refresh the headlines. If you do it once every few seconds, that's probably OK. If you have several filters that need to be refreshed periodically you should be aware that the API proxy limits the frequency of requests to the max of 5 per second. Additional limits on data consumption may be introduced in the future.0
Answers
-
Hi @p.volgger, Eikon Data API does not have streaming capability. The newly released websocket API complements the Eikon API, but requires TREP infrastructure to get data.
There are other streaming market data API's like EMA, which work with Thomson Reuters Enterprise Platform (TREP), and can be used to subscribe to MRN news feed, which seem better suited to your requirement.
0
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛