I need to resolve a chain of historical RICS, e.g. 0#TFI: how do I qualify historical RIC chains ...

...in the API?
The Refinitiv Developer Portal has a working example of Chain Resolution and it is included in Tutorial 15 of the current Postman collection. This works fine, but I have a chain that resolves to "Historical RICs" and so requests need to be qualified. . Can I apply something similar for the chain resolution of 0#TFI: ? At the moment using the tutorial 15 example as is, I get an error message for "0#TFI:" but I do not get with "0#DJI:"
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Search.HistoricalChainInstrument)",
"value": []
}
In in a tick history Time and Sales on demand request in the API I need to specify the following after the instrument list like this extract below (see "ValidationOptions section).
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers" : [
{
"Identifier" : "TIEFJ21",
"IdentifierType" : "Ric"},
{ "Identifier" : "TIEFK21",
"IdentifierType" : "Ric"
}
],
"ValidationOptions": {"AllowHistoricalInstruments": true},
"UseUserPreferencesForValidationOptions": false
},
Best Answer
-
Hello @mark.ringrose,
In my understanding, in order to use an identifier (ChainRIC) as input into any searches or extractions, it has to first be found/recognized by Datascope.
Unfortunately, I could not find this identifier neither via Datascope GUI search nor via API request searches.
However, as DJI chain appears to be 0#.DJI rather then 0#DJI:, perhaps you are looking for 0#.TFII, or perhaps another slightly different chain, can it be that the chain you are looking for is slightly different, according to Eikon search, there are several suggestions of similar chains.
Would it make sense to involve content experts directly via Refinitiv Helpdesk Online -> Content -> RTH, once you are able to identify the required via content, then it can be submitted via API?
0
Answers
-
My mistake - there was an error in the chain RIC in my Postman example. My fault.
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.5K 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
- 560 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
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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 中文论坛