Can't download historical e-mini data from TRTH using REST API
When I request information for the December 2017 e-mini contract (ESZ7) from Oct. 2017 via the REST API in TRTHv2, it fails, telling me that the RIC is invalid. I'm well aware that the RIC was valid, and in fact retrieved it using the Historical Chain resolution in TRTHv2 itself! Retrieval via the website GUI works requesting the same RIC, but is completely impractical for the use case I'm dealing with.
My JSON query:
{
"ExtractionRequest": {
"@odata.type": "TickHistoryRawExtractionRequest",
"Condition": {
"ReportDateRangeType": "Range",
"DateRangeTimeZone": "UTC",
"SortBy": "SingleByRic",
"ExtractBy": "Ric",
"MessageTimeStampIn": "LocalExchangeTime",
"DomainCode": "MarketByPrice",
"QueryStartDate": "2017-10-24T21:30:00.000000Z",
"QueryEndDate": "2017-10-25T21:29:59.999000Z",
"TimeRangeMode": "Inclusive",
"DisplaySourceRIC": false
},
"ContentFieldNames": [],
"IdentifierList": {
"@odata.type": "InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "ESZ7",
"IdentifierType": "Ric"
}
]
}
}
}
The TRTH response:
{
"Notes": [
"All identifiers were invalid. No extraction performed."
],
"IdentifierValidationErrors": [
{
"Message": "Not found",
"Identifier": {
"@odata.type": "#ThomsonReuters.Dss.Api.Content.InstrumentIdentifier",
"Source": "",
"Identifier": "ESZ7",
"IdentifierType": "Ric"
}
}
],
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#RawExtractionResults/$entity",
"JobId": "0x06602e827a501287"
}
Thanks very much for your help.
Best Answer
-
Hi @davidk
The ESZ7 is historical instruments as it had been valid by 12/25/2017. To extract the historical instrument, you need to enable the AllowHistoricalInstruments validation options in the request message. Below is the sample of request.
{
"ExtractionRequest":
{ "@odata.type": "TickHistoryRawExtractionRequest",
"Condition": {
"ReportDateRangeType": "Range",
"DateRangeTimeZone": "UTC",
"SortBy": "SingleByRic",
"ExtractBy": "Ric",
"MessageTimeStampIn": "LocalExchangeTime",
"DomainCode": "MarketByPrice",
"QueryStartDate": "2017-10-24T21:30:00.000000Z",
"QueryEndDate": "2017-10-25T21:29:59.999000Z",
"TimeRangeMode": "Inclusive", "DisplaySourceRIC": false },
"ContentFieldNames": [],
"IdentifierList": {
"@odata.type": "InstrumentIdentifierList",
"InstrumentIdentifiers":
[ { "Identifier": "ESZ7", "IdentifierType": "Ric" } ],
"ValidationOptions":
{
"AllowHistoricalInstruments": true
},
"UseUserPreferencesForValidationOptions": false
}
}
}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
- 697 Datastream
- 1.5K DSS
- 632 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 563 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
- 746 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
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 97 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛