How can investment firms use the insider screener API?
Investment firms can use the insider screener API to add global insider transaction data to research, monitoring and idea-generation workflows. Instead of checking regulatory filings market by market, analysts and data teams can work with a consistent API response across supported jurisdictions.
Common use cases include monitoring a portfolio, screening an investment universe, enriching company research and testing whether insider activity adds useful context to an existing investment process.
Monitor a portfolio or watchlist
A firm can map its tickers, ISINs, LEIs or RICs to canonical insider screener issuers, then retrieve transactions for the matched companies.
This workflow can support:
- Daily monitoring of insider purchases and sales
- Analyst notifications for newly disclosed transactions
- Compliance or risk dashboards covering portfolio companies
- Watchlists for prospective investments
- Coverage of several markets through one data model
Use /api/v1/data/identify/ to resolve your identifiers. For larger lists, /api/v1/data/transactions/by-identifiers/ accepts a batch of identifiers and returns matching transactions within a selected lookback window.
Create a focused daily insider feed
The market feed and transaction endpoints can supply a daily research process without requiring analysts to review every new filing manually.
A firm might filter for:
- Open-market purchases or sales
- Transactions above a minimum USD value
- Executives, directors or other position types
- A specific country, sector, index or market-cap range
- A defined notification or transaction-date window
- Changes representing a meaningful percentage of an insider's holdings
The filters allow each team to define what is material for its mandate. A global equity fund may monitor several markets, while a regional strategy can restrict requests to its investable universe.
Add insider activity to company research
Insider transactions can provide another source of evidence during company review. An analyst can use the API to examine:
- Who traded and their reported position
- Whether the transaction was a purchase, sale or other operation
- The reported price, quantity, currency and USD value
- Holdings before and after the transaction, when disclosed
- The execution, notification and filing dates
- Prior transactions by the same issuer or person
- Filing amendments and whether a record remains current
This data can be displayed in an internal company page, research notebook or investment memo alongside fundamentals, estimates and market data.
Screen for notable insider behaviour
API Research includes screener endpoints that reduce a broad transaction universe to more focused research candidates. Available workflows include:
- Ranking the largest insider purchases or sales
- Finding insiders buying into price weakness
- Combining insider activity with 52-week price extremes
- Reviewing insider behaviour around earnings events
- Ranking insiders using historical performance measures
- Finding recent trades made by higher-rated insiders
- Identifying issuers where strong buying scores coincide with higher-rated buyers
These screens can help an analyst decide where to spend research time. They are inputs to an investment process, not standalone investment recommendations.
Support quantitative research
Data teams can transform the API fields into features for internal models. Examples include:
- Net purchase or sale value over a rolling period
- Number of distinct insiders buying the same company
- Executive purchases compared with broader insider activity
- Transaction value relative to company size
- Changes in an insider's disclosed holdings
- Insider activity before or after earnings events
- Historical returns following an insider's transactions
The API provides normalized fields while retaining source and raw information where available. This makes it possible to start with standardized data and preserve context for review.
Firms should still define their own methodology, validation rules and treatment of missing data. Regulatory reporting requirements and field availability differ between markets.
Enrich internal securities and issuer data
The identifier-resolution and issuer endpoints can connect insider records with an existing security master or research database.
A typical mapping process is:
- Submit the firm's tickers, ISINs, LEIs, RICs or issuer slugs.
- Store the returned insider screener issuer ID and slug.
- Review any ambiguous ticker matches using the candidate country, exchange and MIC.
- Check whether transaction or screener coverage is available.
- Use the canonical mapping for subsequent requests.
This avoids relying on ticker symbols alone, which can be reused across markets.
Feed dashboards, notebooks and data pipelines
The API returns JSON and can be used from Python, R, spreadsheets with API connectors, business-intelligence tools or an internal data platform. The OpenAPI schema can also be used to generate a client or import the API into compatible development tools.
For a durable integration:
- Store API keys in a secret manager.
- Follow the pagination links returned by the API.
- Use stable transaction IDs for deduplication.
- Save both the notification date and execution date.
- Handle
nullvalues because not every regulator reports every field. - Record amendments and current or superseded filing status.
- Use incremental date windows instead of repeatedly downloading the same history.
- Monitor credit and rate-limit headers in automated jobs.
Choose the appropriate API plan
All API plans include core transaction, issuer, person, identifier-resolution and market-feed access. The plans differ in areas such as included credits, request rate, page size and historical scope.
API Research adds the research and screener endpoints used for ranked ideas, insider-performance analysis and more specialized screening workflows.
Review API pricing for current plan limits and endpoint costs. Firms evaluating a larger integration can contact API support to discuss their markets, universe size and intended request volume.
Start with a small research workflow
A practical evaluation does not need a full production pipeline. Start with one market or a small watchlist, retrieve recent transactions, and compare the results with the firm's existing research process.
The following guides cover the first implementation steps: