Unable to get data via Refintiv Data Library (refinitiv.data) Python

You can enable trace in the Python WebSocket, as shown below.

websocket.enableTrace(True)
   
print("Connecting to WebSocket " + url + " ...")
web_socket_app = websocket.WebSocketApp(url, header=headers,
                                        on_message=on_message,
                                        on_error=on_error,
                                        on_close=on_close,
                                        subprotocols=['tr_json2'])

The output looks like this:

Otherwise, you can test the WebSocket connection with the Curl command.

curl --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Host: localhost:9060" --header "Origin: http://localhost:9060&quot; --header "Sec-WebSocket-Key: 4FlPV2h/xF20YXwlt7zBiw==" --header "Sec-WebSocket-Version: 13" --header "x-tr-applicationid: <app key>" --header "Sec-WebSocket-Protocol: tr_json2" -v http://localhost:9060/api/rdp/streaming/pricing/v1/WebSocket

The output looks like this:

Please make sure that 9060 is the correct port by accessing this URL (http://localhost:9060/api/status) via a web browser.

All comments

Thanks for reaching out to us.

I can run it properly.

[stream_connection] - [_run_websocket_listener] - [OMMSTREAMING_PRICING_0.0] connect
    num_attempt : 0
    url         : ws://localhost:9060/api/rdp/streaming/pricing/v1/WebSocket
    headers     : ['User-Agent: Python', 'x-tr-applicationid: <application id>', 'Authorization: Bearer <token>']
    cookies     : None
    transport   : websocket
    subprotocols: ['tr_json2']
[2023-01-06 12:07:19,216] - [sessions.desktop.workspace.0] - [DEBUG] - [112488 - ThreadOMMSTREAMING_PRICING_0.0] - [stream_connection] - [_on_ws_open] - [OMMSTREAMING_PRICING_0.0] on_ws_open

Please share the full Refinitiv Data log when the problem occurred. I would like to verify the version of the RD library and dependencies.

You can also run the following code to test the connection.

import websocket
import threading
import time

url = "ws://localhost:9060/api/rdp/streaming/pricing/v1/WebSocket"
application_id = "x-tr-applicationid: <application id>"
token = "Authorization: Bearer <token>"

headers = ['User-Agent: Python',application_id,token]

def on_message(ws, message):
    print("on message")

def on_error(ws, error):
    """ Called when websocket error has occurred """
    print(error)


def on_close(ws, close_status_code, close_msg):
    """ Called when websocket is closed """

    print("WebSocket Closed")


def on_open(ws):
    """ Called when handshake is complete and websocket is open, send login """

    print("WebSocket successfully connected!")


# Start websocket handshake

print("Connecting to WebSocket " + url + " ...")
web_socket_app = websocket.WebSocketApp(url, header=headers,
                                        on_message=on_message,
                                        on_error=on_error,
                                        on_close=on_close,
                                        subprotocols=['tr_json2'])
web_socket_app.on_open = on_open

    # Event loop
wst = threading.Thread(target=web_socket_app.run_forever)
wst.start()

try:
    while True:
        time.sleep(1)
except KeyboardInterrupt:
    web_socket_app.close()

You can the url, <application id>, and <token> from the Refinitiv Data log.

The output looks like this:

If this code is unable to establish a websocket connection, the problem could be from network settings.

Hi Jiraponse,

Thanks - comparing the headers between yours and mine its clear that I do not have a token, and only have an application ID.

My understanding is that the application ID is the App Key from the Eikon desktop application, what is the application ID here then?

Thanks.

Wesley

Yes, it is an application key.

You can remove token from the headers.

headers = ['User-Agent: Python',application_id]

Please verify the versoin of the RD library that you are using.

I am using the latest one (RD version is 1.0.0).

Hi Jirapongse,

With default company proxy settings:

Explicitly setting proxy to None:

Is there a way to troubleshoot the network settings?

My version of RD library is 1.0.0b25.

You can enable trace in the Python WebSocket, as shown below.

websocket.enableTrace(True)
   
print("Connecting to WebSocket " + url + " ...")
web_socket_app = websocket.WebSocketApp(url, header=headers,
                                        on_message=on_message,
                                        on_error=on_error,
                                        on_close=on_close,
                                        subprotocols=['tr_json2'])

The output looks like this:

Otherwise, you can test the WebSocket connection with the Curl command.

curl --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Host: localhost:9060" --header "Origin: http://localhost:9060&quot; --header "Sec-WebSocket-Key: 4FlPV2h/xF20YXwlt7zBiw==" --header "Sec-WebSocket-Version: 13" --header "x-tr-applicationid: <app key>" --header "Sec-WebSocket-Protocol: tr_json2" -v http://localhost:9060/api/rdp/streaming/pricing/v1/WebSocket

The output looks like this:

Please make sure that 9060 is the correct port by accessing this URL (http://localhost:9060/api/status) via a web browser.

Hi Jirapongse, the port is correct.

Output 1 with default proxy settings:

----------------------- 
--- response header --- 
HTTP/1.1 200 Connection established 

----------------------- 
--- request header --- 
GET /api/rdp/streaming/pricing/v1/WebSocket HTTP/1.1 
Upgrade: websocket 
Host: localhost:9060 
Origin: http://localhost:9060 
Sec-WebSocket-Key: E6cohDP/n2dJqMYLNwX++w== 
Sec-WebSocket-Version: 13 
Connection: Upgrade 
Sec-WebSocket-Protocol: tr_json2 
User-Agent: Python 
x-tr-applicationid: <id> 

----------------------- 
--- response header --- 
HTTP/1.1 301 Moved Permanently Server: BlueCoat-Security-Appliance 
Location:http://10.190.169.68 
Connection: Close 
-----------------------
Connecting to WebSocket ws://localhost:9060/api/rdp/streaming/pricing/v1/WebSocket ...
scheme http is invalid
WebSocket Closed

Is this a firewall issue?

Yes, it is possible.

I found that BlueCoat-Security-Appliance relates to the secure web gateway application.