Inconsistent behavior requesting Historical Market Depth on futures contracts
requestBody={
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryMarketDepthExtractionRequest",
"ContentFieldNames": [],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{ "Identifier": "CLM8", "IdentifierType": "Ric" }],
"ValidationOptions": {
"AllowHistoricalInstruments": "true",
},
"UseUserPreferencesForValidationOptions": "false",
},
"Condition": {
"View": "RawMarketByPrice",
"MessageTimeStampIn": "GmtUtc",
"ReportDateRangeType": "Range",
"QueryStartDate": "2018-04-25T22:00:00.000Z",
"QueryEndDate": "2018-04-26T21:59:59.999Z",
"DisplaySourceRIC": "true"
}
}
}
The above returns
Extraction finished at 2019-02-09 16:42:43 UTC, with servers: tm03n03, TRTH (145.146 secs)
Historical Instrument <RIC,CLM8> expanded to 1 RIC: CLM8.
Total instruments after instrument expansion = 1
and if I simply change the years to 2017 from 2018, I get the following:
Extraction finished at 2019-02-09 16:45:19 UTC, with servers: x03q13
Historical Instrument <RIC,CLM8> expanded to 0 RICS.
Report suppressed because there are no instruments
What am I missing? Both are historical queries...
Best Answer
-
Hi @jwaldron,
The <CLM8> RIC on Market By Price domain (8) is only valid between 2018-03-24 and 2018-06-10, so you will not get RawMarketByPrice data for 2017.
You can verify the availability of RICs on specific domains using HistoricalSearch endpoint. The list of available domain code is in the API Reference Tree.
Request:
POST Search/HistoricalSearch
{
"Request": {
"Identifier": "CLM8",
"IdentifierType": "Ric",
"DomainCodes": [6,8],
"Range": {
"Start": "2003-01-01T00:00:00.000Z",
"End": "2019-02-10T00:00:00.000Z"
}
}
}Response:
{
"@odata.context": "https://hosted.datascopeapi.reuters.com/RestApi/v1/$metadata#Collection(ThomsonReuters.Dss.Api.Search.HistoricalSearchResult)",
"value": [
{
"Identifier": "CLM8",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxDTE04fA",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "1996-01-01T00:00:00.000Z",
"LastDate": "2018-06-10T00:00:00.000Z",
"History": []
},
{
"Identifier": "CLM8",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxDTE04fA",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "8",
"FirstDate": "2018-03-24T00:00:00.000Z",
"LastDate": "2018-06-10T00:00:00.000Z",
"History": []
}
]
}0
Answers
-
Thank you very much for that response... I was able to replicate that information, and now have a feel for how to search this... Are you able to detail how the "domain" compares to "view" in regard to MarketDepth TickHistory? This is what the guide shows as view types for MarketDepth..
<EnumType Name="TickHistoryMarketDepthViewOptions">
<Member Name="RawMarketByPrice" Value="0"/>
<Member Name="RawMarketByOrder" Value="1"/>
<Member Name="RawMarketMaker" Value="2"/>
<Member Name="LegacyLevel2" Value="3"/>
<Member Name="NormalizedLL2" Value="4"/></EnumType>
A couple of those seem to tie out to domains... but not all... can you point me towards the documentation that would provide some clarity around the differences?
Thank you
0 -
Here are some of the domain numbers and corresponding views:
- 7 - RawMarketByOrder
- 8 - RawMarketByPrice
- 9 - RawMarketMaker
I'm not sure if there are domain numbers for the other two, as they are normalized views.
0 -
The "LegacyLevel2" and "NormalizedLL2" view types use Legacy Level 2 RIC, as a source. The Legacy Level 2 RIC is on MarketPrice domain (6). The RIC's structure is <Level 1 MarketPrice RIC> + <special suffix>, i.e. 0700.HKd.
Please note that not all RICs support these view types. You will get IdentifierValidationErrors in response when RICs do not support Legacy Level 2.
You can get the Legacy Level 2 RIC as constituents of a Chain RIC named with "0#" + <Level 1 MarketPrice RIC>, i.e. 0#0700.HK.
For more information about Level 2 RICs, please see this question. Also, below is the definition of the view types.
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
- 689 Datastream
- 1.4K DSS
- 625 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
- 558 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
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 277 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 1.9K Refinitiv Data Platform
- 695 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
- 93 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛