For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
We have been unable to access the token retrieval page since yesterday. Neither https://api.refinitiv.com/auth/oauth2/v1/token nor https://api.refinitiv.com/auth/oauth2/beta1/token works. We get an HTTP 405 error. Could you check your systems, please?
The above error was not the correct. Please check the new error description in my answer.
Hi,
Thank you for your participation in the forum.
Are any of the replies below satisfactory in resolving your query?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Hi,
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
Hello @matthias.biedenkapp
Please be informed that the latest version of the RDP Service discovery API (/streaming/pricing/) is currently v1.
The WebSocket endpoint name in the given screenshot is the old endpoint name. The current name is all XXX-streaming-pricing-api.refinitiv.com DNS names pattern such as apac-1-t3.streaming-pricing-api.refinitiv.com, emea-1-t3.streaming-pricing-api.refinitiv.com, etc.
I suggest you checked the latest version of the Refinitiv Real-Time - Optimized (RRTO) example on the GitHub RDP example or WebSocket API download page.
The RRTO Installation and Configuration Guide document is also useful.
Hello @matthias.biedenkapp
Do you still encounter the issue? Could you please test the HTTP request in the same machine with the following cURL command?
curl --location --request POST 'https://api.refinitiv.com/auth/oauth2/v1/token' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --header 'Authorization: Bearer ' \ --data-urlencode 'username=<Username/Machine ID>' \ --data-urlencode 'password=<Password>' \ --data-urlencode 'grant_type=password' \ --data-urlencode 'scope=trapi' \ --data-urlencode 'takeExclusiveSignOnControl=true' \ --data-urlencode 'client_id=<App Key>'
Alternatively, you may use the "Get Access Token" Postman script to test the connection from the same machine. You can download the Postman script from the RDP APIs download page and see how to setup the Postman in this tutorial.
Sorry, I got the wrong Error message. The real exception is related to the websocket connection.
I can reproduce the error in the API Playground when using the "/streaming/pricing/beta1/" workflow.
The connection to the websocket services could not be established.
