TickHistory Time & Sales data not available via DSS REST API

I am pulling a TickHistory Time & Sales data for a collection of futures. I can do that via DataScope Select GUI. For example,
Instrument: CGZH6
Fields: Trade - Open, Trade - High, Trade - Low, Trade - Price
Range Query: 2006-01-01 00:00:00 to 2007-01-01 00:00:00 UTC
Data is available and everything seemed ok through GUI. However when I submitted the same request through the REST API. I got a 200 Success status_code, but the content said "All Identifiers were invalid".
When I ran the same request for a different instrument CGZM9 over 2008. I did get some valid data back. So there's nothing wrong with my API code. But data availability seemed very sporadic.
I need to do a complete extract of the TickHistory data without gaps.
Best Answer
-
CGZH6 is a historical instrument that was last traded in 2016, as can be seen by doing a historical search on the RIC:
Therefore, to retrieve data, you need to specify in your request that you want to allow historical instruments. By default they are not allowed, hence the "invalid identifiers" message you receive.
Below is the body of a request in Postman that delivers the data. Note the 2 lines in the IdentifierList that contain ValidationOptions (to allow historical instruments), and UseUserPreferencesForValidationOptions (which overrides the user preferences set in the GUI):
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryTimeAndSalesExtractionRequest",
"ContentFieldNames": [
"Trade - Open", "Trade - High", "Trade - Low", "Trade - Price", "Trade - Volume",
"Trade - Exchange Time"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [ { "Identifier": "CGZH6", "IdentifierType": "Ric" } ],
"ValidationOptions": {"AllowHistoricalInstruments": true},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"MessageTimeStampIn": "GmtUtc",
"ApplyCorrectionsAndCancellations": false,
"ReportDateRangeType": "Range",
"QueryStartDate": "2006-01-01T00:00:00.000Z",
"QueryEndDate": "2007-01-01T00:00:00.000Z",
"DisplaySourceRIC": true
}
}
}Hope this helps.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 705 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 569 WebSocket API
- 40 FX Venues
- 16 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
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.2K Refinitiv Data Platform
- 879 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 123 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 919 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 103 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛