WebSocket Connectivity Issue
Dear @umer.nalla , @wasin.waeosri ,
We are able to get the access token as well as do service discovery now. Since we are from emea region we have selected following endpoint and trying to connect to Websocket. However we are not getting any message back
ws://emea-1-t1.streaming-pricing-api.refinitiv.com:443/WebSocket
We have tried telnet on emea-1-t1.streaming-pricing-api.refinitiv.com and we have no connectivity issues at our end.
We are using java as programming language and have used MarketPriceAuthentication.java sample client from https://github.com/Refinitiv/websocket-api/blob/88fc74f8c39f1163f83e3004aeb11729e7d2e6ec/Applications/Examples/java/MarketPriceAuthentication.java
Kindly advise.
Best Answer
-
Hello @kishore.karanam
Firstly, the examples for the RTO connection are available on GitHub - /Applications/Examples/RDP directory. The example that matches your requirement is the MarketPriceRdpGwAuthentication.java example file.
The MarketPriceAuthentication.java example that you have tried is for the local RTDS deployment scenario, not RTO.
Secondly, the RTO WebSocket connection is encrypted, so you need to connect to the "wss://" URL, not just "ws://" URL which is an unencrypted protocol.
Next, please be informed that the RTO is available in multiple capacity levels, currently provided in 3 tiers: small, medium, and large. You need to connect to the WebSocket server that matches your watchlist size/tier based on your credential permission.
You can get the list of the RTO WebSocket server for your connection tier with the Service Discovery API.
Example API Call:
curl --location --request GET 'https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket&dataformat=tr_json2'; \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <access token>'Please replace the <access token> with your access token from the RDP APIs Auth Service.
0
Answers
-
Is there a particular reason you are using Websocket API rather than EMA Java as recommended in an earlier post?
EMA Java is generally much simpler to use than Websocket API and also delivers a higher performance level than Websocket API.
1
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 中文论坛