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.
0
Answers
-
Thank you @zoya faberov0
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 中文论坛