Just started using the API, can someone help with a quick start regarding the following: which ap...

Best Answer
-
Hi @3352edee-c7b3-42de-95ff-77348a2fc138_deprecated_0bbe7cc3-29e3-4fb6-9839-cd518b6f430b
The Websocket API can be used to consume realtime streaming tick data from a realtime data source such as Elektron.
For historical or reference data you will need to use an alternative data source + API such as DataScope Select - REST API
I would recommend you contact the Refinitiv Helpdesk and raise a Content type query to ascertain which data source (and therefore API) you would need to use.
0
Answers
-
Hi @3352edee-c7b3-42de-95ff-77348a2fc138_deprecated_0bbe7cc3-29e3-4fb6-9839-cd518b6f430b
I understand that you spoke to a content specialist who advised that the Corn contractws settlement price for different months can be accessed on Elektron by using different RIC codes.
e.g. CH1=MAR1, CK1=MAY1, CN1=JUL1, CU1=SEP1, CZ1=DEC1 etc.
In view of this you can make a Websocket View Request using the RIC code for the date you are interested in and specify the subset of Fields you wish to request.{
"ID": 3,
"Key": {
"Name": "CZ0"
},
"View": [
"SETTLE",
"SETTLEDATE",
"CONTR_MNTH"
]
}So, for example the above Websocket request should return something like:
RECEIVED:
[
{
"ID": 3,
"Type": "Refresh",
"Key": {
"Service": "ELEKTRON_DD",
"Name": "CZ0"
},
"State": {
"Stream": "Open",
"Data": "Ok",
"Text": "All is well"
},
"Qos": {
"Timeliness": "Realtime",
"Rate": "JitConflated"
},
"PermData": "AwEBkcA=",
"SeqNumber": 8624,
"Fields": {
"CONTR_MNTH": "DEC0",
"SETTLE": 416.25,
"SETTLEDATE": "2018-12-13"
}
}
]You can changed the exact list of fields in the View as per your requirement.
The above request will make a streaming request, i.e. one where you are expecting to receive updates for the RIC as and when they occur. If you are only interested in a Snapshot request, then you should specify Streaming : false in the request message e.g.
{
"ID": 3,
"Streaming" : false,
"Key": {
"Name": "CZ0"
},
"View": [
"SETTLE",
"SETTLEDATE",
"CONTR_MNTH"
]
}The above will ensure you only receive snapshot of the field values at that moment in time. After which the stream will be closed.
Note that if you are going to request multiple RICS then you can make a Batch request.
You can combine a Batch + View to request the required Fields for multiple RICs e.g.{
"ID": 3,
"Streaming" : false,
"Key": {
"Name": [
"CH0",
"CK0",
"CN0",
"CU0",
"CZ0"
]
},
"View": [
"SETTLE",
"SETTLEDATE",
"CONTR_MNTH"
]
}Obviously, before you make any Item requests, you will need to send a Login Request to the server. and ensure a successful Login.
The other thing to note is that if you are requesting individual streaming RICs i.e.not in a Batch, then you will need to use a unique ID for each item you request. You will note that when you make a Batch request, the server allocates a unique ID for each item in the responses you receive back.
0 -
Many thanks for this! As i understand it correctly: this settlement request returns the latest known settlement, is that correct? So when requested today before market close, i will get the settle from yesterday, and when requested after market close today, it will be the settlement of today?
0 -
Hi @3352edee-c7b3-42de-95ff-77348a2fc138_deprecated_0bbe7cc3-29e3-4fb6-9839-cd518b6f430b
You are welcome.
Regards the exact settlement value timing, I would refer this back to the Content helpdesk - as they are best placed to answer content related questions.
I would also confirm with the Content team that the SETTLE field is indeed the correct field for your requirements - as there are several Price type fields being returned for those RICs in question.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
- 717 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 中文论坛