@brook

You can find the ERT in Cloud - Installation and Configuration Guide in WebSocket API document page. It will give you a basic concept of how to implement ERT in Cloud WebSocket application (for any languages).

The basic flow for ERT in Cloud WebSocket application are following:

1. Send a HTTP POST request message with username (Machine ID), password and Clent ID (appkey) information to RDP Authentication service to obtain access token, refresh token, expiration time and scope information
2. Send a HTTP GET request message with access token to RDP Realtime Service Discovery service to get lists of ERT in Cloud WebSocket streaming server endpoints, ports and location information (VIPs)
3. Connect to ERT in Cloud WebSocket endpoint from step (2)
4. Once a WebSocket connection is established, sends a JSON Login request message with access token ERT in Cloud WebSocket server
5. Once the Login request message is accepted by ERT in Cloud WebSocket server, the application can send item subscription request messages to ERT in Cloud endpoint.
6. Re-issue RDP Authentication service before token expiration to keep the session opens.
7. Once the application receives a new access token, application must re-send a new JSON Login request message with a new access token and refresh attribute value false in the JSON message to ERT in Cloud WebSocket server.

Hi @brook, that website cannot be used for testing, since it is a simple echo test. For using the ERT websocket protocol, the user needs to send in the login message, with the Access token included in the header or key, or else the request will be rejected by the gateway servers.

Please use the Python or Java sample provided in the downloads section - Elektron Real Time in Cloud Examples to get a working sample implementation.

Hi Gurpreet! Thanks for the response!

We are currently use golang. And, I am able able to send a get request to receive lists of endpoints and ports. What's the endpoint to establish a connection?

I am following the guild below:

https://developers.refinitiv.com/en/api-catalog/refinitiv-real-time-opnsrc/refinitiv-websocket-api/quick-start

The service discovery returns a list of available endpoints and the user should choose the one which is geographically closest to them.

For most users in Americas region, this will be one of the servers in the US-EAST location - like

amer-3.pricing.streaming.edp.thomsonreuters.com

Yes, I am using one of the endpoints. Below a sample endpoint.

wss://amer-3.pricing.streaming.edp.thomsonreuters.com:443/WebSocket

However, it connects and disconnects right away.

You will have to provide more details on your API/tools/language/framework etc.

Are you using the Python sample, if not can you please try the sample.

If this issue is happening with Python sample as well, then there is some infrastructure issue. Is there a proxy or firewall in the network. Is it configured to allow port 443, secure websocket protocol.

Hello @brook

You can find Elektron WebSocket API Go examples in the Refinitiv/websocket-api example/go page. Please note that they are example for connecting to a local TREP server. I suggest you check the market_price_authentication.go which shows how to sends a login credential (EDP/RDP access token) with the login message.

The ERT in Cloud WebSocket API examples are in EDP(RDP) example GitHub page. They provides ERT in the Cloud WebSocket examples with C#, Java and Python languages for developers, so you need to apply the ERT in the Cloud logic from those example to your Go application.