We succesfully received token via https://api.refinitiv.com:443/auth/oauth2/v1/token
and then we are trying to call https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket.
But this https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket does not return anything.
One day ago, the request https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket correctly returned a list of endpoints.
If i try to call https://api.refinitiv.com/streaming/pricing/v1/?transport=websocket via browser it return
code"401"message"Authorization header is missing"status"Unauthorized"
so we has an network access.
What it can be?
Are you using C#?
If so, there is an issue due to the increase in the number of services added over the weekend, the response has started being chunked.
As a result of this, if you are using the C# example or another scenario where you are checking the service discovery response content length - this would now return -1 and something like the following would now fail:
if (webResponse.ContentLength > 0)
so the above should be replaced with something like:
if (webResponse.GetResponseHeader("Transfer-Encoding").Equals("chunked") || webResponse.ContentLength > 0)
Hope this helps.
If you were using our C# service discovery example on Github, these will be updated shortly.
When making a request to the discovery URL you have to provide an Authorisation bearer token as demonstrated in our examples:
Also, please refer to the Websocket RTO Quickstart - QuickStart | Refinitiv Developers for details on how to run the Python example
Could you please try the Service Discovery request with the following curl command? Please replace the <access_token> with your Access Token from the RDP Auth Token service (Note: please notice a space between text 'Bearer' and the access token).
curl --location --request GET 'https://api.refinitiv.com/streaming/pricing/v1/' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer <access token>'
If you still encounter errors from the curl command, I suggest you contact the RDP support team via https://my.refinitiv.com/ website to help you verify the issue.
Please select the "Pricing - Refinitiv Data Platform" product on the my.refinitiv.com website, and give them the following information:
Hope this helps.
If you are using the github example, please note that as well as the above fix, there was another minor fix applied to the code - so recommend you download the latest version.