No response received using WebSocket API via the Enterprise Apigee Gateway

Naveen
Naveen Newcomer
edited May 15 in WebSocket API

We are attempting to connect to the Refinitiv RealTime – Optimized WebSocket API via the Enterprise Apigee Gateway to retrieve currency rates. While we’ve successfully established connectivity through the gateway and receive a 101 WebSocket status, we’re encountering issues when sending the login JSON payload. The target system does not return any response. We would appreciate it if someone from your team could assist us in troubleshooting this issue. Thank you

Tagged:

Answers

  • Gurpreet
    Gurpreet admin

    Hello @Naveen

    Most likely, your gateway is blocking/modifying the request/response. If you have the means to monitor and capture the traffic on your gateway, it would help in the diagnostics. I presume you have already verified that your application works when this gateway is not in the play - i.e. from home network etc.

    If you are looking for RTO logs, then you would have to raise a support ticket at LSEG MyAccount. We do not have any visibility into the RTO backend services or the system logs.

  • Naveen
    Naveen Newcomer

    We have been successful in calling without Apigee Gateway in play. There are some differences in Apigee on how rest API is called vs Websocket API. Though it says websocket is supported in Apigee, we are trying to figure out what custom configurations are required. The debug log in Apigee gateway didn't provide JSon response details, just 101 success. and then it immediately disconnects. We did get Login successful once with the Json body payload sent after connecting. but is it very intermittent. Have raised a case with RTO to review the logs and help with this troubleshooting

Categories