IDN_RDF to get bonds prices
SENT:
{
"ID": 2,
"Key": {
"Name": [
"91282CFK2=RRPS"
],
"Service": "IDN_RDF"
},
"View": [
"BID"
],
"Streaming": true
}
RECEIVED:
[
{
"ID": 2,
"Type": "Status",
"State": {
"Stream": "Closed",
"Data": "Ok",
"Text": "Processed 1 total items from Batch Request. 1 Ok."
}
},
{
"ID": 3,
"Type": "Status",
"Key": {
"Service": "IDN_RDF",
"Name": "91282CFK2=RRPS"
},
"State": {
"Stream": "ClosedRecover",
"Data": "Suspect",
"Text": "Json conversion error."
}
}
]
not sure why its showing JSON conversion error , any clue pls ?
Best Answer
-
Hello @avinash.jain
I have tested your View request message with my local ADS 3.7.3.L1 and the RTO connection scenarios. You JSON request message is valid, and I did not encounter any issues on my end.
SENT:
{
"ID": 2,
"Key": {
"Name": [ "91282CFK2=RRPS"],
"Service": "ELEKTRON_DD"
},
"View": ["BID"],
"Streaming": true
}
RECEIVED:
[
{
"ID": 2,
"Type": "Status",
"State": {
"Stream": "Closed",
"Data": "Ok",
"Text": "Processed 1 total items from Batch Request. 1 Ok."
}
}
]
RECEIVED:
[
{
"ID": 3,
"Type": "Refresh",
"Key": {
"Service": "ELEKTRON_DD",
"Name": "91282CFK2=RRPS"
},
"State": {
"Stream": "Open",
"Data": "Ok"
},
"Qos": {
"Timeliness": "Realtime",
"Rate": "JitConflated"
},
"PermData": "AwEBaJfA",
"SeqNumber": 7776,
"Fields": {
"BID": 98.359375
}
}
]I am assuming that you are connecting to a local deployed RTDS server. Beside my colleague's suggestion above, I think you and your Market Data Team should contact the ADS support team to verify the issue on the ADS server (as WebSocket API is the server-side API).
You can contact the ADS support team via https://my.refinitiv.com/content/mytr/en/helpandsupport.html website.
1
Answers
-
There doesn't seem to be anything wrong with your request. I tried it within my environment, and works properly. The only difference between my request and yours is that I did not specify the 'Service'. I don't know anything about your environment or what ADS (WebSocket server) you are connecting to. Normally, you don't need to specify the Service as it is usually defaulted to the market data service within your environment. I would suggest you not specify the Service.
If this doesn't help, you may need to contact your Market Data Services team to understand what is happening and confirm the name of the Service should be.
1
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 中文论坛