No start and end time in the response of HistoricalChainResolution?

Good day experts,
I'm trying the 'get historical chain' operation, the request body is:
{
"Request": {
"ChainRics": [
"0#.SPX"
],
"Range": {
"Start": "2008-01-01T00:00:00.000Z",
"End": "2008-01-01T00:00:00.000Z"
}
}
}
And the response looks like:
...
"Constituents": [
{
"Identifier": ".SPX",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwuU1BYfA",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6"
},
{
...
It missed the 'Start' and 'End' time fields?
e.g., in the ' TICK HISTORY FOR DATASCOPE SELECT 13.2 REST API USER GUIDE''s example:
...
"Constituents": [
{
"Identifier": "HOF0",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxIT0Ywf
A",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"Start": "2008-01-01T00:00:00.000Z",
"End": "2008-01-01T00:00:00.000Z"
},
{
...
Is that true or I miss some settings in the http request?
Best Regards,
Frederic
Best Answer
-
Hi @Frederic.Li,
I have verified the returned value of HistoricalChainResolution in the API Reference Tree and Metadata. There is no Start and End time field in response, so it likely is that the example result in the REST API User Guide document is not correct. To get the Valid Start and End time, you can pass the Constituents to HistoricalBulkSearch
I will contact TRTH support to verify the issue.
0
Answers
-
Thank you Veerapath, looks like the HistoricalBulkSearch does not touch/display the history chain itself and when a constituent was added into that chain.
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.4K 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
- 559 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
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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 中文论坛