how to View old and new ric with change date in HistoricalReference on demand raw extract
want to get this kind of data
sdate edate old new current
-----------------------------------------------------
2014.08.24 2099.01.01 8321.HK 0048.HK 0048.HK
2015.06.15 2099.01.01 DEA0V6ZA.D 00E1.D 00E1.D
2015.06.15 2099.01.01 DEA0V6ZA.SG 00E1.SG 00E1.SG
2015.06.15 2099.01.01 DEA0V6Y7.D 00E2.D 00E2.D
2015.06.15 2099.01.01 DEA0V6Y7.SG 00E2.SG 00E2.SG
2015.06.15 2099.01.01 DEA0V6Y8.D 00E3.D 00E3.D
2015.06.15 2099.01.01 DEA0V6Y8.SG 00E3.SG 00E3.SG
2015.06.15 2099.01.01 DEA0V6YU.D 00E4.D 00E4.D
2015.06.15 2099.01.01 DEA0V6YU.SG 00E4.SG 00E4.SG
2015.06.15 2099.01.01 DEA0V6ZC.D 00E5.D 00E5.D
2015.06.15 2099.01.01 DEA0V6ZC.SG 00E5.SG 00E5.SG
2015.06.15 2099.01.01 DEA0V6ZR.D 00E6.D 00E6.D
2015.06.15 2099.01.01 DEA0V6ZR.SG 00E6.SG 00E6.SG
2015.06.15 2099.01.01 DEA0V6ZF.D 00E7.D 00E7.D
2015.06.15 2099.01.01 DEA0V6ZF.SG 00E7.SG 00E7.SG
2015.06.15 2099.01.01 DEA0V6ZU.D 00E8.D 00E8.D
2015.06.15 2099.01.01 DEA0V6ZU.SG 00E8.SG 00E8.SG
2015.06.15 2099.01.01 DEA0V6YS.D 00E9.D 00E9.D
2015.06.15 2099.01.01 DEA0V6YS.SG 00E9.SG 00E9.SG
how do I get it ?
Best Answer
-
It can get a bit complex to sort out by first appearance of the RIC in the historical reference result. So alternatively, like to suggest taking a look at
{{protocol}}{{host}}{{api}}Search/HistoricalSearch
{
"Request": {
"Identifier": "KYG211351195",
"IdentifierType": "Isin",
"Range": {
"Start": "1995-01-01T00:00:00.000Z",
"End": "2017-01-01T00:00:00.000Z"
}
}
}we get back multiple entries such as
{
"Identifier": "0048.HK",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwwMDQ4LkhLfA",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6",
"FirstDate": "1996-01-01T00:00:00.000Z",
"LastDate": "2017-11-06T00:00:00.000Z",
"History": []
},To make sense, we concentrate only on DomainCode=6, MarketPrice.
FirstDate and LastDate are the dates when the sinstrument was first valid and last valid,
with the exception of the instrument which is still valid, then LastDate will be the request date.
Does this request work better for your use case?
0
Answers
-
I think a good way is HistoricalReferenceExtractionRequest.
Please refer to REST API Tutorial 10 - Historical Reference
Similar to this:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC", "CUSIP", "ISIN", "SEDOL", "Issuer OrgID", "Exchange Code", "Currency Code", "Change Date"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "DEA0V6ZA.D",
"IdentifierType": "Ric"
},
{
"Identifier": "0048.HK",
"IdentifierType": "Ric"
},
{
"Identifier": "00E1.SG",
"IdentifierType": "Ric"
},
{
"Identifier": "00E2.D",
"IdentifierType": "Ric"
}
],
"ValidationOptions": {"AllowHistoricalInstruments": true},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"StartDate": "1996-05-01T00:00:00.000Z",
"EndDate": "2017-05-31T23:59:59.000Z"
}
}
}0 -
This request gives me data in this form
RIC Change Date
------------------------
"CKF.AX" "2017/01/01"
"BVIC.L" "2017/01/01"
"BVIC.L" "2017/03/22"
"BVIC.L" "2017/03/28"
"BVIC.L" "2017/03/30"
"BVIC.L" "2017/04/11"
"BVIC.L" "2017/07/11"
"BVIC.L" "2017/07/13"
"BVIC.L" "2017/07/15"
"BAER.S" "2017/01/01"
"BAER.S" "2017/07/27"
"BAER.S" "2017/10/18"
"600059.SS" "2017/01/01"
"600059.SS" "2017/07/31"but along with change date, I also want to know what was this RIC before change date? What it has changed to ? and What is current RIC ?
0 -
Depending on the use case. Let's take an example of RIC
0048.HK -> 0048.HK^A12-> 8321.HK
Once we have run the previous request, we know the common Isin = KYG211351195
We can issue
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest",
"ContentFieldNames": [
"RIC", "CUSIP", "ISIN", "SEDOL", "Issuer OrgID", "Exchange Code", "Currency Code", "Change Date"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "KYG211351195",
"IdentifierType": "Isin"
}
],
"ValidationOptions": {"AllowHistoricalInstruments": true},
"UseUserPreferencesForValidationOptions": false
},
"Condition": {
"StartDate": "1990-05-01T00:00:00.000Z",
"EndDate": "2017-05-31T23:59:59.000Z"
}
}
}The received data will contain multiple change dates with RICs across this ISIN, with increasing change date.
The first set of changes carries the original RIC 0048.HK. The first occurrence of
0048.HK^A12 is when it was first valid. Then we have multiple changes of
0048.HK^A12 and the last set of changes contains RIC 8321.HK, the first one being when it was first valid.
Do you see how Historical Reference can be used to derive the RICs?
0 -
This kind of works as this gives me this data,
how do I know on which date Ric actually changed ?
0 -
This should be the first raw with the changed RIC, in the column "Change Date"
0 -
Can't understand, can you elaborate ??
0 -
Thanks it works but How to send single request for multiple ISIN's or Do I have to send Individual request for each ISIN ? Like in on Demand Extraction there is identifier List Dict in JSON format, something like that..
0 -
Yes. With this request type, you can only submit one identifier at a time.
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 中文论坛