WebSocket Connectivity Issue

kishore.karanam

Dear @umer.nalla , @wasin.w ,

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.

wasin.w

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.

umer.nalla

Hi @kishore.karanam

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.