A lot of IPO research starts as manual filing review: S-1s, F-1s, amendments, 424B4s, effectiveness notices, ticker changes, exchange hints, and post-listing performance. That works for one company. It breaks down if you want to build watchlists, backtests, screens, or systematic models.

The IPOGrid API is meant to make that workflow structured.

Docs:

https://ipogrid.com/docs

API reference:

https://ipogrid.com/api/v1/docs

OpenAPI:

https://ipogrid.com/api/v1/openapi.json

What you can pull

IPOGrid exposes structured company, filing, news, chart, article, and outcome data. The useful modeling chain is usually:

companies → filings → extracted terms / consensus → outcomes / news

That means you can start with an issuer, resolve it to a durable CIK, add filing events, add deal terms, then join to post-listing outcomes. IPOGrid’s docs specifically recommend using CIK as the durable issuer key because tickers can drift, collide, or point to units and warrants instead of the common-stock IPO.

Example feature families

Here are the kinds of features I’d extract for a financial model.

Issuer identity features

CIK

issuer name

ticker hint

resolved ticker

exchange

sector

issuer kind

market family

deal type

operating company vs SPAC vs fund vs follow-on

These are basic filters, but they matter. Mixing operating IPOs, SPACs, funds, direct listings, and follow-ons in the same model is usually garbage-in, garbage-out.

Filing timeline features

first registration date

latest amendment date

number of amendments

days from initial filing to effectiveness

days from latest amendment to pricing

presence of S-1, F-1, S-11, 424B4, 424B1, 8-A, EFFECT

final prospectus filed or not

recent filing activity count

filing recency bucket

The docs call out SEC filing events such as registrations, amendments, final prospectuses, effectiveness notices, and 8-A registrations as explicit research surfaces.

Deal term features

offer price

price range low

price range high

range midpoint

shares offered

gross proceeds

underwriters

use of proceeds

unit details

warrant terms

range revision direction

range revision magnitude

priced above range / in range / below range

IPOGrid exposes extracted offer price, range, shares, proceeds, underwriters, unit details, warrants, and use-of-proceeds fields so you do not have to reopen every filing manually.

Consensus / listing features

resolved listing date

resolved exchange

resolved offer price

resolved shares

resolved proceeds

latest terms snapshot

classification

consensus ticker

consensus listing fields

The API supports company lookups with includes such as latest_terms, classification, consensus, filings, news, and financial_snapshot.

Outcome features

trading start date

first close

1D return

week-one close

week-one return

current performance

offer-to-first-close return

offer-to-week-one return

IPOGrid has outcome rows for first close, 1D return, week-one close, and post-listing performance.

Market context features

gross proceeds by week

prospectus counts

final prospectus counts

first-day returns by sector

filing activity by form family

sector-level IPO volume

recent IPO temperature

The chart API supports metrics such as gross proceeds, prospectus counts, final prospectus counts, and first-day returns grouped by sector, form family, or status over fixed or trailing windows.

Basic API calls

Use an API key for the richer endpoints:

export IPOGRID_API_KEY="your_key_here" 

Find companies and include the useful joins:

curl -H "Authorization: Bearer $IPOGRID_API_KEY"  "https://ipogrid.com/api/v1/companies?scope=all&kind=operating&include=latest_terms,classification,consensus" 

Fetch company detail by ticker or CIK:

curl -H "Authorization: Bearer $IPOGRID_API_KEY"  "https://ipogrid.com/api/v1/companies/spcx?include=filings,news,latest_terms,classification,consensus,financial_snapshot" 

Pull recent final prospectus filings:

curl -H "Authorization: Bearer $IPOGRID_API_KEY"  "https://ipogrid.com/api/v1/filings?form_type=424B4&filing_date_from=2026-06-01&include=company,terms" 

Pull recent outcomes:

curl -H "Authorization: Bearer $IPOGRID_API_KEY"  "https://ipogrid.com/api/v1/outcomes?trading_start_date_from=2026-06-01&limit=100" 

Pull public articles without auth:

curl "https://ipogrid.com/api/v1/articles?limit=30" 

The public article feed works without authentication; deeper company, filing, and outcome data uses API key bearer auth.

Backtest shape

A clean IPO backtest should freeze the cohort before looking at outcomes.

For example:

1. Select operating-company IPOs only.
2. Require a final prospectus or effective status.
3. Exclude SPACs, funds, vehicles, direct listings, and follow-ons.
4. Resolve each issuer to CIK.
5. Pull only filing and term data available as of the cohort date.
6. Join outcomes after trading starts.
7. Measure first-day and week-one returns against the offer price.

IPOGrid’s research workflow docs make the same basic point: freeze the cohort definition first, then join market bars or outcomes only after the cohort date to avoid leaking future information.

Example model table

A row in a modeling dataset might look like this:

cik company_name issuer_kind sector exchange form_family initial_filing_date latest_amendment_date final_prospectus_date effective_date trading_start_date days_initial_to_effective days_final_prospectus_to_trade amendment_count offer_price range_low range_high range_midpoint priced_vs_range shares_offered gross_proceeds underwriter_count has_warrants is_unit_deal first_close day1_return_pct week1_close week1_return_pct sector_ipo_count_26w sector_avg_day1_return_26w 

That table can feed normal financial modeling workflows: screening, regression, ranking, clustering, risk controls, or event studies.

Caveats

Do not treat latest terms as historical truth. Latest snapshots are useful for current watchlists, but historical tests should use the filings and market data that existed around the test date. IPOGrid’s freshness docs explicitly warn not to silently fill missing historical fields with today’s values.

Also separate clocks carefully. SEC filing dates, SEC acceptance times, pricing dates, and trading dates are different events. A Friday filing, Monday effectiveness notice, and Tuesday first trade should not be collapsed into one timestamp.

Finally, ticker logic needs care. Units, warrants, and share classes can trade separately. A ticker hint is not always the same thing as the security your model is trying to study. For anything serious, resolve to CIK first, then verify the traded instrument.

Practical use cases

A few useful models you can build from this:

IPO readiness screen: find effective or recently amended operating IPOs with exchange listing signals and extracted terms.

Pricing-change model: compare initial range, revised range, final offer price, and sector conditions.

Day-one return model: join final prospectus terms to first close and sector-level IPO context.

Week-one fade model: compare first close to week-one close.

Filing-momentum model: count amendments, form changes, and final prospectus timing.

Sector heat model: use chart data to track issuance volume, proceeds, and first-day returns by sector.

The important part is not just having IPO data. It is having issuer, filing, term, and outcome data joined in a way that does not leak future information into the model.