HistoricalChainResolution - Returns Invalid RICs as "Valid"

I am trying to search individual RICs from a Chain RIC by using HistoricalChainResolution.
Then found that retuned list of RICs actually contains Invalid RICs as well ( while status indicates "Valid" )
For instance, Below request will return bunch of individual RICs.
Request :
URL : {{protocol}}{{host}}{{api}}Search/HistoricalChainResolution
Body:
{
"Request": {
"ChainRics": [
"0#CDSBNKJPR="
],
"Range": {
"Start": "2022-05-01T00:00:00.000Z",
"End": "2022-05-16T00:00:00.000Z"
}
}
}
Return
{
"@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#Collection(DataScope.Select.Api.Search.HistoricalChainInstrument)",
"value": [
{
"Identifier": "0#CDSBNKJPR=",
"IdentifierType": "ChainRIC",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHwwI0NEU0JOS0pQUj18",
"Description": "Historical Chain",
"InstrumentType": "Unknown",
"Status": "Valid",
"Constituents": [
{
"Identifier": "AOZR10YUSAC=R",
"IdentifierType": "Ric",
"Source": "",
"Key": "VjF8MHgzMDAwMDAwMDAwMDAwMDAwfDB4MzAwMDAwMDAwMDAwMDAwMHx8fHx8fHxBT1pSMTBZVVNBQz1SfA",
"Description": "Historical Instrument",
"InstrumentType": "Unknown",
"Status": "Valid",
"DomainCode": "6"
},
...... ( Bunch of RICs will follow, but some are non existing RICs as well as valid RICs )
Actually , In above example, one of retuned RIC "AOZR10YUSAC=R" is actually no longer exist ( so invalid RIC ) , but somehow those invalid RICs are retuned with the valid RICs , "Status" of those RICs indicated as "Valid" as well as other existing ( valid ) RICs.
Is there anyway to exclude such invalid RICs from the returned RICs??
Thank you
Best Answer
-
Hi @noboru.maruyama4 ,
I have tried this chain RIC with real time feed, and even that is returning a list of invalid RICs in the chain. This seems like a data issue, and I would recommend that you open a content ticket with my.refinitiv.com and speak with a data content expert.
0
Answers
-
@GurpreetHi
Many thanks for your advise, Actually I could replicate same behaver even with Eikon Excel ( Invalid individual RICs appear from a chain RIC )
so I raised an Query to Dara Content team.
Thank you for your advise
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
- 280 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 中文论坛