Different views for Websocket API request

Is it possible to have a different view in the request for different ric's? Like:
{
"ID": 2,
"Key": {
"Name": "EUR="
},
"View": [
"PRIMACT_1",
"CTBTR_1",
"QUOTE_DATE"
]
},
{
"ID": 3,
"Key": {
"Name": "CZ0"
},
"View": [
"SETTLE",
"SETTLEDATE"
]
}
Best Answer
-
Hello @3352edee-c7b3-42de-95ff-77348a2fc138_deprecated_0bbe7cc3-29e3-4fb6-9839-cd518b6f430b
Yes, it is possible. Each item request message can has a different view.
Example from market_price.py:
req_msg = '[{"ID":2,"Key":{"Name":"EUR="},"View":["PRIMACT_1","CTBTR_1","QUOTE_DATE"]},{"ID":3,"Key":{"Name":"CZ0"},"View":["SETTLE","SETTLEDATE"]}]'
ws.send(json.dumps(json.loads(req_msg)))Example results: result.txt
The RIC CZ0 has a few updates but it still receives a refresh message with fields "SETTLE" and "SETTLEDATE".
Please note that you can test and verify the Elektron WebSocket JSON request message with your local ADS server (3.2.1 and above) with the WebSocket API Try it Now! Documentation. The documentation is available Elektron WebSocket API download page. You can find more detail about this tool and Elektron WS JSON at Elektron WebSocket API Quick Start - Connecting to TREP page.
0
Answers
-
thanks! What is the meaning of the id 2 or 3 here? Does it matter?
0 -
The ID (2 or 3 here) is a unique identifier for your request. The response message from server will contain that same identifier, so that application can associate responses to requests.
The ID should be unique for every request that an application sends.
0 -
Hello @3352edee-c7b3-42de-95ff-77348a2fc138_deprecated_0bbe7cc3-29e3-4fb6-9839-cd518b6f430b
The ID is a reference of each item request stream. The ID must be used to identify which stream you want to modify (such as close item). It can also be used to match the request and responses.
Item request:
{
"ID": 7,
"Key": {
"Name": "TRI.N"
}
}
<br>Item close:
{
"ID": 7,
"Type": "Close"
}0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 698 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 2.9K Elektron
- 1.5K EMA
- 257 ETA
- 565 WebSocket API
- 40 FX Venues
- 16 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2.1K Refinitiv Data Platform
- 799 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 232 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 101 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛