while using websockets with Real-Time - Optimized, how do I get the chain information to even start?
Question:
while using websockets with Real-Time - Optimized, how do I get the chain information to even start?
- What service? "ELEKTRON_DD" seems to just return "not found" for everything; e.g, 0#C 0#/C, 0#.FTSE, etc.
- What URL do I use for the websocket connection?
I've modified a github sample (MarketPriceEdpGwServiceDiscoveryExample) and am successully getting an auth token and pricing after discovering
services with https://api.refinitiv.com/streaming/pricing/v1/.
When I send messages like this:
{
"ID": 2,
"Streaming": false,
"Key":
{
"Name":
[
"<#/C:",
"0#C:",
]
}
}
I get a resonse like this:
[
{
"ID": 3,
"Type": "Refresh",
"Key": {
"Service": "ELEKTRON_DD",
"Name": "0#/C:"
},
"State": {
"Stream": "NonStreaming",
"Data": "Ok"
},
"Qos": {
"Timeliness": "Realtime",
"Rate": "JitConflated"
},
"PermData": "AwEBSRDA",
"SeqNumber": 2655,
"Fields": {}
}
]
There is nothing in that response to expand chains with.
n.b. Despite having the right RIC, I really suspect that you cannot expand chains using the ELEKTRON_DD service or possibly not through the streaming price URL.
I am well aware of this code:
https://github.com/Refinitiv-API-Samples/Article.WebSocketAPI.DotNet.DotNetCoreChainExpanderApp
But it sure doesn't connect to anything directly in the "elektron cloud". I can of course point it at our local ADS (which we are trying to get rid of), but that isn't Cloud.
Thank you
Best Answer
-
I can subscribe and get data just fine (one of the instruments in your request is invalid). I used the service discovery example from github.
SENT on session1:
{
"ID":2,
"Key":{
"Name":[
"<#/C:",
"0#C:"
],
"Service":"ELEKTRON_DD"
},
"Streaming":false
}
RECEIVED on session1:
[
{
"ID":2,
"State":{
"Data":"Ok",
"Stream":"Closed",
"Text":"Processed 2 total items from Batch Request. 2 Ok."
},
"Type":"Status"
}
]
RECEIVED on session1:
[
{
"Fields":{
"BCAST_REF":"GRA",
"CONTEXT_ID":2540,
"CURRENCY":"USc",
"DDS_DSO_ID":8294,
"DSPLY_NAME":"CORN",
"DSPLY_NMLL":null,
"LINK_1":"CH1",
"LINK_10":"CZ2",
"LINK_11":"CH3",
"LINK_12":"CK3",
"LINK_13":"CN3",
"LINK_14":"CU3",
"LINK_2":"CK1",
"LINK_3":"CN1",
"LINK_4":"CU1",
"LINK_5":"CZ1",
"LINK_6":"CH2",
"LINK_7":"CK2",
"LINK_8":"CN2",
"LINK_9":"CU2",
"MKT_SECTOR":"1",
"NEWS":"YYYY",
"NEWS_TIME":"22:29:05",
"NEXT_LR":"1#C:",
"PREF_LINK":"1#C:",
"PREV_DISP":0,
"PREV_LR":null,
"PROD_PERM":91,
"RDNDISPLAY":208,
"RDN_EXCHD2":"CBT",
"RDN_EXCHID":"CBT",
"RECORDTYPE":200,
"REF_COUNT":14,
"SPS_SP_RIC":".[SPSCBOTVAE1"
},
"ID":4,
"Key":{
"Name":"0#C:",
"Service":"ELEKTRON_DD"
},
"PermData":"AwEBkcA=",
"Qos":{
"Rate":"JitConflated",
"Timeliness":"Realtime"
},
"SeqNumber":191,
"State":{
"Data":"Ok",
"Stream":"NonStreaming"
},
"Type":"Refresh"
}
]
RECEIVED on session1:
[
{
"ID":3,
"Key":{
"Name":"<#/C:",
"Service":"ELEKTRON_DD"
},
"State":{
"Code":"NotFound",
"Data":"Suspect",
"Stream":"Closed",
"Text":"**The record could not be found"
},
"Type":"Status"
}
]Similarly:
SENT on session1:
{
"ID":2,
"Key":{
"Name":"0#.FTSE",
"Service":"ELEKTRON_DD"
}
}
RECEIVED on session1:
[
{
"Fields":{
"ACTIV_DATE":null,
"ALIAS":null,
"BCAST_REF":null,
"CONTEXT_ID":6700,
"CURRENCY":null,
"DDS_DSO_ID":12488,
"DSPLY_NAME":"FTSE 100 INDEX",
"DSPLY_NMLL":null,
"INSTU_NAME":null,
"LONGLINK1":".FTSE",
"LONGLINK10":"AVST.L",
"LONGLINK11":"AVV.L",
"LONGLINK12":"AZN.L",
"LONGLINK13":"BAES.L",
"LONGLINK14":"BARC.L",
"LONGLINK2":".AD.FTSE",
"LONGLINK3":"AAL.L",
"LONGLINK4":"ABF.L",
"LONGLINK5":"ADML.L",
"LONGLINK6":"AHT.L",
"LONGLINK7":"ANTO.L",
"LONGLINK8":"AUTOA.L",
"LONGLINK9":"AV.L",
"LONGNEXTLR":"1#.FTSE",
"LONGPREVLR":null,
"MSG_VER":null,Please contact content-support at MyRefinitiv to understand it.
0
Answers
-
Thank you @Gurpreet @Maury.Hill response received, please review if this helped
0 -
Thanks. Seeing this response reminded me I had specified a View and the fields for the Chain were missing from that. I forgot I was applying a View.
Effectively, I was embarrassingly filtering out the very fields I was looking for.
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 中文论坛