Refinitv Tick History Historical Search for Chain RIC
Chain RIC 0#SIRT- gives incorrect end date (2017-05-06) using 'ResultsBy': 'Entity, however without 'ResultsBy': 'Entity it gives correct end date:
with 'ResultsBy': 'Entity
when sending request
@{'Request': {'@odata.context': 'http://selectapi.datascope.refinitiv.com:83/RestApi.Help/$metadata#DataScope.Select.Api.Search.HistoricalSearchRequest',
'IdentifierType': 'ChainRIC',
'Identifier': '0#SIRT-:',
'Range': {'Start': '1996-01-01T00:00:00.000Z',
'End': '2021-12-31T23:59:59.000Z'},
'ResultsBy': 'Entity'}}
to below
https://selectapi.datascope.refinitiv.com/RestApi/v1/Search/HistoricalSearch
it returns
@{'@odata.context': 'https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#Collection(DataScope.Select.Api.Search.HistoricalSearchResult)',
'value': [{'Identifier': '0#SIRT-:',
'IdentifierType': 'Ric',
'Source': '',
'Key': 'VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwwI1NJUlQtOnw',
'Description': 'Historical Instrument',
'InstrumentType': 'Unknown',
'Status': 'Valid',
'DomainCode': '6',
'ValidFrom': '1996-06-04T04:43:43.200Z',
'ValidTo': '2017-05-06T14:09:09.000Z',
'FirstDate': '1996-06-04T00:00:00.000Z',
'LastDate': '2017-05-06T00:00:00.000Z',
'History': [{'Ric': '0#SI-:',
'ValidFrom': '1996-06-04T04:43:43.200Z',
'ValidTo': '2016-01-23T14:34:11.415Z',
'FirstDate': '1996-06-04T00:00:00.000Z',
'LastDate': '2016-01-23T00:00:00.000Z'},
{'Ric': '0#SIRT-:',
'ValidFrom': '2016-01-23T14:34:11.415Z',
'ValidTo': '2017-05-06T14:09:09.000Z',
'FirstDate': '2016-01-23T00:00:00.000Z',
'LastDate': '2017-05-06T00:00:00.000Z'}]}]}
Without 'ResultsBy': 'Entity : End date shows 2022-07-09
{
"Request": {
"Identifier": "0#SIRT-:",
"IdentifierType": "ChainRIC",
"Range": {
"Start": "1996-01-01T00:00:00.000Z",
"End": "2021-12-31T00:00:00.000Z"
},
"ResultsBy": "Ric"
}
}
{
"@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#Collection(DataScope.Select.Api.Search.HistoricalSearchResult)",
"value": [
{
"Identifier": "0#SIRT-:",
"IdentifierType": "ChainRIC",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwwI1NJUlQtOnw",
"Description": "Historical Chain",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "2016-01-23T00:00:00.000Z",
"LastDate": "2022-07-09T00:00:00.000Z",
"History": []
}
]
}
Also, why does the 1st API response shows 0#SIRT-: as RIC
And the chain0#SIRT-: is active till date(why doesnt end date shows as todays date)
Best Answer
-
Hello @Vinod A ,
The results can differ because Results By Entity specifier is only relevant to individual RICs not to chains. There is no entity that is associated with the chain. This is also why, I believe, if you include the specified the result it comes out as RIC, the service does not process the request as valid.
I suggest to additionally verify this with our content experts via Refinitiv Helpdesk Online for a definitive answer about this content, as well as to find any relevant recommendations.
1
Answers
-
Thank you @zoya faberov0
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 中文论坛