Strange RIC from EquitySearch

Hi,
I'm executing an EquitySearch API call, with an ISIN : CH0011075394, and specifying the market SWX. I obtain a RIC like this one: ZURZn.S^D99
That seems to be wrong, since it does not return with further calls in HistoricalData and it is not returned from the DataScope web application. What am I doing wrong?
Parameter of the EquitySearch are:
Identifier = CH0011075394;
IdentifierType = IdentifierTypes.Isin;
ExchangeCodes = GetExchanges("SWX");
PreferredIdentifierType = IdentifierType.Ric;
Best Answer
-
The syntax including a "^" indicates a delisted RIC. The original RIC is before the "^", so in this case it is ZURZn.S, which delivers results in a historical search:
Delisting can be due to various reasons. In this particular case it is due to a (series of) name changes, because ZURZn.S became ZURZn.VX, then ZURN.VX and is now ZURN.S !
Added later after further investigation:
In the equity search results the current RIC ZURN.S is not under SWX but under VTX. Same in the DSS GUI, same inside Eikon. Strange, it looks like all blue chips are under VTX, whereas other instruments are under SWX (like ALLN.S, ISIN CH0008837566).
Added yet later after more investigation:
Blue chips initially moved from SWX to VTX. When the blue chips quoted on VTX returned to SWX it was decided not to change the exchange for the blue chips, in
order to distinguish the Blue Chip RICs.As you forced the search to deliver SWX results it delivered the most recent one for SWX which was the very old delisted RIC (hence the strange syntax), from the time before the move to VTX.
If you search using exchange VTX it delivers the most recent one for VTX, which is the current RIC.
In case you want some context: SWX fact sheet
To make it easy:
Filter on exchanges SWX and VTX, and add a criteria to deliver only current instruments:
"AssetStatus": "Active",
Full request in Postman:
{
"SearchRequest": {
"AssetStatus": "Active",
"AssetCategoryCodes": null,
"SubTypeCodes": null,
"CurrencyCodes": null,
"CompanyName": null,
"Description": null,
"DomicileCodes": null,
"ExchangeCodes": [
"SWX", "VTX"
],
"FairValueIndicator": null,
"FileCodes": null,
"GicsCodes": null,
"OrgId": null,
"Ticker": null,
"Identifier": "CH0011075394",
"IdentifierType": "Isin",
"PreferredIdentifierType": "Ric"
}
}0
Answers
-
I added a solution in the form of a Postman example, after you accepted my initial response. Hope you will find this useful.
0 -
@ChristiaanMeihsl Thanks for yout effort, yes this is an improvement on the way we create requests, thank you.
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
- 687 Datastream
- 1.4K DSS
- 621 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 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
- 276 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
- 669 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
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 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
- 48 中文论坛