Going delisting data
Hi everybody! I am currently exploring methods to obtain a comprehensive list of companies along with their respective delisting announcement dates, utilizing Codebook. This requirement is akin to the functionality provided by the advEvents application. While I am able to generate a list of delisted companies through a specific formula from the screener app, my primary objective is to extract both the company name and the date of its delisting announcement. The ultimate aim of this endeavor is to facilitate future analyses that delve into the reasons behind each delisting event, rather than merely identifying the occurrence of such events.
Thank you!
Best Answer
-
Hi @vitali
I would suggest you use the Search API.
For example, here is a request to retrieve the first 25 delisted companies and the delisted dates:
rd.discovery.search(
filter = "OrganisationStatus xeq 'Delisted'",
select ="DocumentTitle, DelistedDate, OrganisationStatus",
top = 25
)This will provide a good start to further your analysis. I would also suggest you review this article around the Search API and what you can do.
1
Answers
-
Thank you, I really appreciate it!
0 -
I am reaching out for further assistance following your previous recommendation to utilize the Search API for my project. The integration has been successful, but I've encountered an obstacle with configuring the filters. Specifically, I am having difficulty identifying the appropriate
PropertyNames
to use within the "filter" parameter, as these were not detailed in the documentation provided, particularly in the Building Search into your Application Workflow.Could please you direct me to the section of the documentation that lists the available
PropertyNames
, or provide guidance on how to access these values?0 -
Hi @vitali
The Property Names are defined within the Metadata section of that article. There are many hundreds of Properties which can be retrieved via the metadata API. Within the "related articles" section, you will see a reference to "build queries easily using the Search API...". That article is very useful to pull down and hunt for properties for you to access within your Searches. Because the Search environment is very rich and powerful, that article hopefully provides a better way for developers to figure out how to pull down the appropriate property names for use.
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 中文论坛