Failed to get Futures contracts according to chain ric via websocket API

Hi, i failed to get the all Future contracts according to use the chain RIC(e.g. 0#HSI:) by websocket API, which the error message is "*The record could not be found". it's the venue not support this request or is there something error in request message? Please kindly advise, thanks.
Best Answer
-
Hi @jarfery.du
Can you confirm the exact JSON Request you are sending? Also, are you connecting to local TREP/ADS or ERT in Cloud?
I just tried the following:
{
"ID":2,
"Key":{
"Name":[
"0#HSI:"
],
"Service":"ELEKTRON_DD"
}
}and I received back:
{
"Fields":{
"BCAST_REF":".HSI",
"CONTEXT_ID":2866,
"CURRENCY":"HKD",
"DDS_DSO_ID":4196,
"DSPLY_NAME":"HANG SENG INDEX",
"DSPLY_NMLL":"\u6046\u751f\u6307\u6578",
...truncated for forum....
"LINK_2":"HSIQ0",
"LINK_3":"HSIU0",
"LINK_4":"HSIZ0",
"LINK_5":"HSIH1",
...truncated for forum....
"RDN_EXCHD2":"HFE",
"RDN_EXCHID":"HFE",
"RECORDTYPE":120,
"REF_COUNT":5,
"SPS_SP_RIC":".[SPSHKFOMDVAE2"
},
"ID":3,
"Key":{
"Name":"0#HSI:",
"Service":"ELEKTRON_DD"
},Is it possible you missed the end ':' - because if I try
{
"ID":2,
"Key":{
"Name":[
"0#HSI"
],
"Service":"ELEKTRON_DD"
}
}I also get back
"Text":"*The record could not be found"
0
Answers
-
Thank you for your prompt reply.
I used the wrong API(Market price domain) to retrieve Futures contract before, and I just tried to use batch request to retrieve Futures contracts in Cloud, which responds with error message "Access Denied: User req to PE(9017)", it means that we haven't permission to subscribe chain ric data yet. Here is our Machine ID "GE-A-00456807-3-3957".
I also extract a sample JSON request/respond message as below:
a). Request JSON message:
SENT on Session1:
{
"ID": 12,
"Key": {
"Name": [
"0#HSI:"
],
"Service": "ELEKTRON_DD"
}
}
b). Respond JSON message:
RECEIVED on Session1:
[
{
"ID": 12,
"Type": "Status",
"State": {
"Stream": "Closed",
"Data": "Ok",
"Text": "Processed 1 total items from Batch Request. 1 Ok."
}
}
]
{
"ID": 13,
"Type": "Status",
"Key": {
"Service": "ELEKTRON_DD",
"Name": "0#HSI:"
},
"State": {
"Stream": "Closed",
"Data": "Suspect",
"Code": "NotEntitled",
"Text": "Access Denied: User req to PE(9017)"
}
},
0 -
Hi @jarfery.du
I have emailed your local Refinitiv account team - so they may get in touch directly - but I recommend you also attempt to contact them to discuss changes to your account permissions.
0 -
Thank you so much!
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 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
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛