How do I pull HistoricTickData from a company that moved from NYSE to NASDAQ?
Both EXC.O and HON.O are RICS from companies that recently (in 2019 and 2021 respectively) moved from NYSE (NYQ feed) to NASDAQ (NSQ feed). Now when I pull minutebars for them using those RICS, the history stops when they moved (so no history from when they were on NYSE).
How do I get the older databars from when they were listed on NYSE?
Can I get that consolidated data in one pull using a different type of identifier or does it require a different RIC?
Best Answer
-
Hello @jori88 ,
Intraday data may not necessarily be available for an instrument, for the whole duration when Price History at end of day is captured.
DSS/RTH API is able to retrieve the data set that is available for the time that it is available.
A couple of things you can do to learn more of the availability of the content:
1. The quickest and most straightforward programmatically is to run a HistoricalSearch.
For example:
{{protocol}}{{host}}{{api}}Search/HistoricalSearch
{
"Request": {
"Identifier": "HON.O",
"IdentifierType": "Ric",
"Range": {
"Start": "1996-01-01T00:00:00.000Z",
"End": "2021-10-11T00:00:00.000Z"
}
}
}Resulting in:
{
"@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#Collection(DataScope.Select.Api.Search.HistoricalSearchResult)",
"value": [
{
"Identifier": "HON.O",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxIT04uT3w",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "2021-05-11T00:00:00.000Z",
"LastDate": "2021-11-09T00:00:00.000Z",
"History": []
},
{
"Identifier": "HON.O",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxIT04uT3w",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "9",
"FirstDate": "2015-05-02T00:00:00.000Z",
"LastDate": "2021-11-09T00:00:00.000Z",
"History": []
}
]
}Domain = 6 is MarketPrice domain. So it would not make sense to request it prior to 2021.05.11 as it is not available.
2. HistoricalReferenceExtractionRequest will give you more details. In some cases not straightforward to understand in my opinion, and may require an expert to interpret, but if I really wish to know the whole story behind the changes, I run a HistoricalReferenceExtractionRequest. For example:
{{protocol}}{{host}}{{api}}Extractions/ExtractWithNotes
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC",
"Start date",
"Change Date",
"Expiration Date",
"Exchange Code"
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{"Identifier": "HON.O", "IdentifierType": "Ric" }
],
"ValidationOptions": {
"AllowHistoricalInstruments": true
},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"StartDate": "2000-01-01T00:00:00.000Z",
"EndDate": "2021-11-10T00:00:00.000Z"
}
}
}And these results:
...
{
"IdentifierType": "Ric",
"Identifier": "HON.O",
"RIC": "HON",
"Start date": null,
"Change Date": "2020-10-03",
"Expiration Date": null,
"Exchange Code": "NYQ"
},
{
"IdentifierType": "Ric",
"Identifier": "HON.O",
"RIC": "HON",
"Start date": null,
"Change Date": "2020-12-05",
"Expiration Date": null,
"Exchange Code": "NYQ"
},
{
"IdentifierType": "Ric",
"Identifier": "HON.O",
"RIC": "HON",
"Start date": null,
"Change Date": "2021-03-31",
"Expiration Date": null,
"Exchange Code": "NYQ"
},
{
"IdentifierType": "Ric",
"Identifier": "HON.O",
"RIC": "HON.O",
"Start date": null,
"Change Date": "2021-05-11",
"Expiration Date": null,
"Exchange Code": "NSQ"
}
...in this case, hold a clue on the Exchange move.
3. By contacting Refinitiv content experts via Refinitiv Helpdesk Online -> Content -> DSS, as a customer, you can obtain an authoritative answer to content-related questions, suspected issues, in other words, in-depth expertise.
0
Answers
-
Hello @jori88 ,
You can request PriceHistory before and after the change, in one pull, for example:
{{protocol}}{{host}}{{api}}Extractions/ExtractWithNotes
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.PriceHistoryExtractionRequest",
"ContentFieldNames": [
"File Code",
"RIC",
"Trade Date",
"Last Trade Price",
"Universal Close Price",
"Alternate Close Price",
"High Price",
"Low Price",
"Open Price",
"Volume Weighted Average Price",
"Turnover",
"Volume",
"Accumulated Volume Unscaled",
"Bid Price",
"Asset Type",
"Quote ID",
"Bid Yield",
"Exchange Code",
"Currency Code"
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{ "Identifier": "EXC.O", "IdentifierType": "Ric" }
],
"ValidationOptions": { "AllowHistoricalInstruments": true },
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"ReportDateRangeType": "Range",
"QueryStartDate": "2014-01-24T00:00:00.000Z",
"QueryEndDate": "2021-08-31T00:00:00.000Z"
}
}
}Resulting in full available history.
ValidationOptions -> AllowHistoricalInstruments and UserPreferences = False options specified
should allow the request to look for the history on these instruments beyond historical changes.
0 -
Thank you,
Above indeed seems the correct solution for a PriceHistoryExtractionRequest.
I'm trying to do a TickHistoryIntradaySummariesExtractionRequest and also when I add "ValidationOptions": { "AllowHistoricalInstruments": true }, I still don't get anything on "HON.O" before 2021-05-11.
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TickHistoryIntradaySummariesExtractionRequest",
"ContentFieldNames": [
"Open", "High", "Low", "Last", "Volume",
"Close Ask",
"Close Bid",
"High Ask",
"High Bid",
"Low Ask",
"Low Bid",
"No. Asks",
"No. Bids",
"No. Trades",
"Open Ask",
"Open Bid",
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{"Identifier": ric, "IdentifierType": "Ric"} for ric in rics],
"ValidationOptions": {"AllowHistoricalInstruments": True, "AllowInactiveInstruments": True},
"UseUserPreferencesForValidationOptions": False
},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
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 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
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛