RRT websocket login messages
I have noticed that when we try to send a new login message to the RRT websocket session, the session is often closed by the remote party. I suspect this is due to a malformed login message sent by us. An example login we might send is:
SENT on wss://eu-west-1-aws-1-sm.optimized-pricing-api.refinitiv.net/WebSocket:
{ "ID": 1, "Domain": "Login", "Key": { "NameType": "AuthnToken", "Elements": { "ApplicationId": "256", "Position": "10.121.25.73", "AuthenticationToken": <authtoken> } } }
I have a copy of the documentation `WEBSOCKET API FOR PRICING STREAMING AND REAL-TIME SERVICES PROTOCOL SPECIFICATION AND DEVELOPERS GUIDE`, but it is very light on detail when it comes to login and authentication.
The specific questions I think will allow me to solve this are:
* When my authentication token expires, is it correct to send a new Login message on the same stream ID with Type Refresh?
* Does the Login stream always have to be on ID 1?
* If I receive a response to a login telling me that the Login stream is closed (Stream State Error), how should I recover from that? Do I need to disconnect from the websocket?
If you have any documentation better than the one I mention above it would be great if you could direct me to it. I am aware of the example code but that does not clarify these points either.
Many thanks
Best Answer
-
Hi @b
If you haven't already, I suggest you refer to the Developer Community for details related to connecting and logging into a WebSocket server. You will find examples demonstrating connecting, login, and login refresh details.
To answer your specific question, when you refresh your token, you need to provide the "Refresh" indicator, i.e.
{
"ID": 1,
"Domain": "Login",
"Key":
{
"NameType": "AuthnToken",
"Elements":
{
"ApplicationId": "256",
"Position": "10.121.25.73",
"AuthenticationToken": <authtoken>
}
},
"Refresh" = false
}0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛