Overview
Room-In-A-Name (RIAN) is designed for front-office and compliance teams to determine how much trading capacity remains before a disclosure threshold is crossed. The feature tells you how many shares are up or down and what percentage you are away from the next reportable threshold.
It is available to view in the user interface (UI) and in a structured format via API.
Data is available for only the latest file upload and is available after the file run is completed.
For cases where two or more different instruments pertaining to the same issuer are aggregated together in the rule result, we will include the headroom in both independently. This means that the grouping logic applied by the Shareholding Disclosure rules might not be reflected in the RIAN output.
UI
API
An API user can access the API at the below URLs:
Documentation: {company-name}-api.fundapps.co/swagger
Room in a name extract: {company-name}-api.fundapps.co/v1/roominaname
Results not calculated: {company-name}-api.fundapps.co/v1/roominaname/errors
FAQ
Q. What is the rule coverage?
A. The RIAN feature covers major, short-selling, and takeover rules. There are some rules where RIAN as a concept does not make sense, e.g. US 13F, where it triggers when your combined holdings of 13F securities (i.e. not a single issuer) need to be considered. For this rule, we do not calculate RIAN.
In other rules or versions of rules, nuanced complexities are not yet captured because they may be specific to only a few situations. For example, delta hedging in Japan. In such cases, FundApps decides not to support it.
For results that are not calculated successfully, you can see these by accessing the following RIAN errors API endpoint: {company-name}-api.fundapps.co/v1/roominaname/errors
For a list of rules NOT covered by our RIAN service, please access the following link.
Q. How do I request more RIAN coverage, and how does FundApps evaluate requests?
A. We welcome your input on potential enhancements, such as expanding RIAN coverage, through our Community portal, where requests are reviewed and considered for future updates.
While we are not currently focusing on expanding RIAN coverage, all requests are evaluated like any other feature request. Our team will carefully assess the request's complexity/effort and weigh it against the value our client base as a whole would receive. Requests with strong support from other users and clients are more likely to be prioritized for consideration.