Research API, combine "Views" selectors.
Hello everyone! I'm currently progressing on a project focused on companies that have been delisted. For this project, I'm utilizing the Refinitiv Search API. I've successfully managed to extract data on US companies that were delisted, including the reasons for their delisting, which are currently limited to two categories: Acquisition and Merger.
response = rd.discovery.search(
view = "Organisations",
filter = "OrganisationStatus xeq 'Delisted' and RCSCountryHeadquartersLeaf eq 'Uni ted States'",
select ="DocumentTitle,CommonName, DelistedDate, OrganisationStatus,DTCharacteristics, FormOfTransactionCode, ReasonDelisted",
top = 1000
)
Given these constraints, I've decided to make the best of the available data.
My current objective is to delve deeper into the specifics of Acquisition and Merger deals to enable the calculation of Delisting Returns for these companies. To achieve this, I've been exploring the DealsMergersAndAcquisitions View, which offers a plethora of fields that could potentially aid in my analysis. However, I've encountered a significant hurdle: the API does not support the simultaneous use of two Views.
What I aim to do is integrate certain selectors from the DealsMergersAndAcquisitions View into the Organisation View or combine data from two views for the same companies into one. This integration would allow me to maintain a comprehensive list of delisted companies, complete with reasons for delisting and detailed information about the corresponding deals. Does anyone know how to accomplish this integration effectively?
Would appreciate any help! Thank you in advance!
Best Answer
-
Hi @vitali
The Search service does not support the ability to specify a list of views as you discovered. However, there is the option of using 'SEARCH_ALL' which should cover every View. What this may do is introduce hits/results that you are not interested in, i,e. more data than you need. However, because Search does provide filtering, you can filter out hits based on relevant criteria. For example, within the Search article, you can review some of the Common Properties as a way to filter unwanted data. Properties such as: 'SearchAllCategoryv3', 'RCSAssetCategory', 'RCSTRBC2012' can potentially help. There is not a specific property that filters out Views but I believe some of the above are pretty close to aligning with the View organization. Because Search is so rich and granular, this does require more investigation. What really aids in this activity is utilizing the browser capabilities as presented in the "Building queries easily using Refinitiv's Search API.." article. Using that, you have a nice way of looking at all properties and their values as well as the domain of values available within navigator properties. This does provide a nice way of understand how data is categorized and thus much easier for you to build intelligent filters.
Hope this helps
0
Answers
-
Hi, @nick.zincone! Thanks for your response! Could you possibly shed some light on why the additional fields I'm utilizing are not displaying?
OfferingType,AcquirerStockPriceOnAnnouncementDay,AcquirerRIC,AcquirerBusinessDescriptionLong,TradingValue,AnalystEstimatedValue
:
response = rd.discovery.searc
view = "SearchAll
filter = "OrganisationStatus xeq 'Delisted' and RCSCountryHeadquartersLeaf eq 'United States'",
select ="DocumentTitle,OfferingType,CommonName,AcquirerStockPriceOnAnnouncementDay,AcquirerRIC,AcquirerBusinessDescriptionLong,TradingValue,AnalystEstimatedValue, DelistedDate, OrganisationStatus,DTCharacteristics, FormOfTransactionCode, ReasonDelisted",
top = 1000,
)Just the same output, without additional selectors.
0 -
Hi @vitali
These data properties are not populated based on your request. For example:
In general, when there is no data available, nothing is returned for that property. You can either use the browser to review values to figure which properties would possibly be relevant or of interest to you or open a content ticket and ask a specialist what data you are after.
I usually utilize the browser to give me a picture of what is available. For example:0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛