Cannot authenticate with WS API

CT Grid Support
CT Grid Support Newcomer
in WebSocket API

We are getting either Type: Ping as response (instead of State/Data/Ok), or 500 Internal Server Error. It was working correctly yesterday, but no outages reported. Anyone seeing this too?

Tagged:

Best Answer

Answers

  • Gurpreet
    Gurpreet admin

    @CT Grid Support

    Can you provide more details - which endpoint are you connecting to and what is the RIC? I presume you are connecting to cloud and not a local enterprise platform.

    I tried amer-3 in cloud multiple times and was able to get data.

  • CT Grid Support
    CT Grid Support Newcomer

    Right now I am getting 500 in response to request sent to

    https://api.refinitiv.com/auth/oauth2/beta1/token

  • Gurpreet
    Gurpreet admin

    I can see that you are still using the beta2 URL. Please note the change to v1

  • CT Grid Support
    CT Grid Support Newcomer

    Actually right now the auth URL started to work but still the endpoint replies with Type: Ping when we try to open WS connection. We expect Data: Ok there. The endpoint we use is emea-1.pricing.streaming.edp.thomsonreuters.com . I will try Python script later, but is there anything wrong with this endpoint?

  • Gurpreet
    Gurpreet admin

    Yes, there seems to be some issue with emea-* endpoint. If you wait long enough (about 20 seconds), your will receive this status message:

    RECEIVED:
    [
      {
        "Domain":"Login",
        "ID":1,
        "Key":{
          "Name":"AQIC5wM2LY4SfczkHaJTMllYQCXlINhiYt6Zt4BPpVp0R%2F8%3D%40AAJTSQACMjAAAlNLABM3NDM1NjUwNTYyMjY5MzM0ODI0AAJTMQACMzM%3D%23"
        },
        "State":{
          "Code":"Timeout",
          "Data":"Suspect",
          "Stream":"Closed",
          "Text":"A21: Access Denied. Timed out waiting for response from DACS server. Try request again."
        },
        "Type":"Status"
      }
    ]

    I will raise this internally. Meanwhile please use other ednpoints like amer-2 or amer-3.

Categories