Does the WebSocket API have any additional reference documentation?
The WebSocket API Developer Guide contains some great reference material, examples and message details used within the Websocket interface. However, there are some areas where I need more information. While I can puruse the examples and determine how functionality works, it would be useful to have such details documented. Things that standout that would be helpful.
- Is there anymore information around the service name or service ID?
When using other market data APIs, the developer can see the available services from the connected ADS. Is this information available programmatically?
- The examples utilize some kind of keep-alive protocol using ping messages.
When receiving a login response, I can see elements such as: ClientToServerPingInterval etc.
- What domains are supported?
The developer guide only references a few but it's not clear what is supported and the structure/request associated with each.
- The examples define that a subprotocol ("tr_json2") is required upon a connection. I don't see this documented anywhere.
Note: I'm not asking for the answers to these questions, but rather if there is or will be documentation that will answer questions like these.
Best Answer
-
The team will continue to incorporate more content into the documentation suite to help fill some of the gaps you have mentioned. The next version of documentation should contain many of the things you are asking about and we will upload it here when it becomes available, as well as include it in the distribution packages that are made available.
0
Answers
-
Hi Nick, here is the JSON OMM specification
on hub, EWA omm structure is following this specification. And in this document you can also find the meaning of each omm message key words.
0 -
This document doesn't address the types of questions I posted above nor is available to customers as an official EWA document.
0 -
Hi nick,
There is no more official documents for EWA except the documents in EWA package, I suggest you can try to find some documents about TREP or ADS, they may contains some more information about the service ID and domains.
0 -
Great. Thanks Brian.
0
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛