How to Find Dilution Events Programmatically

Querying parsed, classified offering events instead of scraping EDGAR — what an API-first approach looks like.

The shortest distance between "I want to screen for stocks raising capital" and a usable dataset is not EDGAR. It is an API that has already done the parsing, classification, and normalization. The work involved in building that pipeline in-house is substantial, and for most use cases the value is in the screening, not in the plumbing.

What an API-first dilution dataset looks like

A useful dilution-events API exposes events as structured records with these properties:

• Ticker and CIK. Joined to a master security identifier table so events are queryable per issuer.
• Filing date and effective date. Filings hit at a specific timestamp; takedowns sometimes price the same day, sometimes later.
• Event type. Underwritten public offering, bought deal, registered direct, ATM activation, ATM draw, PIPE, ELOC, resale registration, warrant exercise.
• Gross and net proceeds. In dollars.
• Shares issued. Absolute count and as a percentage of pre-offering shares outstanding.
• Offer price. In dollars per share for priced offerings.
• Discount to prior close. As a percentage.
• Underwriter or placement agent. Counterparty entity, normalized.
• Parent shelf reference. S-3 registration number.
• Source filings. URLs to the underlying 8-K, 424B5, etc.

That field set is the minimum viable schema. Anything less requires the user to do their own parsing per event.

What you can build on top

With a structured feed, a few common applications:

1. Daily alerts on dilution events meeting screening criteria (e.g., offerings >20% of shares outstanding, in stocks with positive 30-day returns).
2. Backtests of post-offering drift conditioned on event type, sector, size, and structure — see what is post-offering drift.
3. Watchlist management: track issuers with active shelves, ATMs, or ELOCs and surface utilization changes.
4. Portfolio risk monitoring: flag held positions when their underlying issuers file new offerings.
5. Strategy research: build event-driven short-side strategies — see how to backtest a short-selling strategy and how to build a stock dilution screener.

What an API saves you

The cost of in-house implementation is rarely the initial scrape — it's the ongoing maintenance of a parsing layer that breaks every time the SEC's EDGAR templates change, the addition of new filing types as the regulatory landscape shifts, and the handling of edge cases (multi-class shares, foreign private issuers, recently merged entities). Each of those problems is solvable but compounds over time.

An API-first approach lets you treat dilution events as data and focus on the analysis. The trade-off is the recurring cost of the data source — for most non-trivial research uses, that cost is a small fraction of the engineering time it replaces.

Query patterns

Typical query patterns for a dilution-events API:

• By date range: "All offerings between 2026-01-01 and 2026-06-30."
• By ticker or CIK: "All dilution events for ticker XYZ in the last three years."
• By event type: "All ATM activations announced in the last 90 days."
• By size threshold: "All offerings where shares issued exceeded 25% of pre-offering shares outstanding."
• By structure characteristic: "All registered directs with warrant coverage in healthcare names."

The API's value compounds with the richness of the query language. A REST endpoint that returns all events with basic filters is useful; one that supports composite queries (event type + size + sector + outcome) is meaningfully better.

Latency expectations

Different use cases require different freshness:

• Daily research is fine with end-of-day capture (events available within hours of filing).
• Event-driven alerts need sub-hour latency.
• Algorithmic execution on event news requires real-time or near-real-time feeds, which adds operational complexity.

Most short-side research falls into the first two categories.

Related reading

For the underlying mechanics: how to find equity offering announcements in SEC filings; how to track shelf registration takedowns; market-data sources for systematic short-selling research; market-data APIs for algorithmic trading in 2026.

Where Alphanume fits

Alphanume's Dilution Events API implements the schema above — every event normalized, classified, and linked to its source filings, queryable via REST. The dataset covers shelf registrations, takedowns, ATMs, PIPEs, ELOCs, and resale registrations across the US-listed universe.

Explore the Dilution Events dataset →