Why is the identifier invalid when trying to use a RIC Root?
I'm currently trying to extract futures data for a particular commodity using the following payload using the the "https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractRaw" end point.
However it returns saying that the identifier is invalid even though this is the correct RIC root.
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.ElektronTimeseriesExtractionRequest",
"ContentFieldNames": [
"RIC",
"RIC Root",
"Trade Date",
"Expiration Date",
"Last Trading Day",
"High",
"Last",
"Low",
"Open",
"Open Interest",
"Volume"
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{"Identifier": "KW", "IdentifierType": "RICRoot"}
]
},
"Condition": {
"StartDate": "2016-08-01T13:00:00.000-05:00",
"EndDate": "2016-09-01T13:00:00.000-05:00"
}
}
}
Best Answer
-
@mike-petrut Hi,
Initially when I looked at this I thought maybe it was a validation option AllowHistoricalInstruments acting as a false restricting the use of this identifier type:
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.ElektronTimeseriesExtractionRequest",
"ContentFieldNames": [
"RIC",
"RIC Root",
"Trade Date",
"Expiration Date",
"Last Trading Day",
"High",
"Last",
"Low",
"Open",
"Open Interest",
"Volume"
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "KW",
"IdentifierType": "RICRoot"
}
],
"ValidationOptions": {
"AllowHistoricalInstruments": true,
"AllowInactiveInstruments": true,
"AllowLimitedTermInstruments": true,
"AllowOpenAccessInstruments": true,
"AllowSubclassImport": true,
"AllowUnsupportedInstruments": false,
"ExcludeFinrAsPricingSourceForBonds": false,
"UseConsolidatedQuoteSourceForCanada": false,
"UseConsolidatedQuoteSourceForUsa": false,
"UseDebtOverEquity": false,
"UseExchangeCodeInsteadOfLipper": true,
"UseOtcPqSource": false,
"UseUsQuoteInsteadOfCanadian": true
},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"StartDate": "2016-08-01T13:00:00.000-05:00",
"EndDate": "2016-09-01T13:00:00.000-05:00"
}
}
}However on checking the above it was still returning the same.
I am checking the use of using this RIC Root/RICRoots with a Tick History template with the Specialists to see whether this is expected.
As an alternative to RIC Root I used Chain RIC just to check if that retrieved anything:
{
"Identifier": "0#KW:",
"IdentifierType": "ChainRIC"
}There were about 360 records returned, I paste the 1st 6 below:
RICRIC RootTrade DateExpiration DateLast Trading DayHighLastLowOpenOpen InterestVolumeKWH7^1KW01/08/201614/03/201714/03/2017457.5452451452292801235KWH8^1KW01/08/201614/03/201814/03/2018
1270KWH9^1KW01/08/201614/03/201914/03/2019
0KWK7^1KW01/08/201612/05/201712/05/2017467.75464462465.25111933434KWK8^1KW01/08/201614/05/201814/05/2018
630KWK9^1KW01/08/201614/05/201914/05/2019
0KWN7^1KW01/08/201614/07/201714/07/2017476.75473.5470.2547116117733
I will respond back on use of RIC Root here when I have more detail on this.
Best regards,
Gareth
1
Answers
-
According to the Tick History REST API User Guide, RICRoot is not in the list of supported instrument formats.
You may need to contact the Tick History support team directly via MyRefinitiv to confirm this.
Otherwise, you need to use a RIC Root with the search endpoints to get all instruments.
0 -
As per @Jirapongse 's comment RIC Root is not among those Identifier Types supported. My recommendation would be to use the Chain RIC: 0#KW: 'KCBT Hard Red Winter Wheat Composite Commodity Future Chain Contracts - CBoT'0
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 中文论坛