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.<\/h1>\n
The IPOGrid API is meant to make that workflow structured.<\/p>\n
Docs:<\/p>\n
https:\/\/ipogrid.com\/docs<\/a><\/p>\n API reference:<\/p>\n https:\/\/ipogrid.com\/api\/v1\/docs<\/a><\/p>\n OpenAPI:<\/p>\n https:\/\/ipogrid.com\/api\/v1\/openapi.json<\/a><\/p>\n IPOGrid exposes structured company, filing, news, chart, article, and outcome data. The useful modeling chain is usually:<\/p>\n companies \u2192 filings \u2192 extracted terms \/ consensus \u2192 outcomes \/ news<\/p>\n 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\u2019s 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.<\/p>\n Here are the kinds of features I\u2019d extract for a financial model.<\/p>\n CIK<\/p>\n issuer name<\/p>\n ticker hint<\/p>\n resolved ticker<\/p>\n exchange<\/p>\n sector<\/p>\n issuer kind<\/p>\n market family<\/p>\n deal type<\/p>\n operating company vs SPAC vs fund vs follow-on<\/p>\n 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.<\/p>\n first registration date<\/p>\n latest amendment date<\/p>\n number of amendments<\/p>\n days from initial filing to effectiveness<\/p>\n days from latest amendment to pricing<\/p>\n presence of S-1, F-1, S-11, 424B4, 424B1, 8-A, EFFECT<\/p>\n final prospectus filed or not<\/p>\n recent filing activity count<\/p>\n filing recency bucket<\/p>\n The docs call out SEC filing events such as registrations, amendments, final prospectuses, effectiveness notices, and 8-A registrations as explicit research surfaces.<\/p>\n offer price<\/p>\n price range low<\/p>\n price range high<\/p>\n range midpoint<\/p>\n shares offered<\/p>\n gross proceeds<\/p>\n underwriters<\/p>\n use of proceeds<\/p>\n unit details<\/p>\n warrant terms<\/p>\n range revision direction<\/p>\n range revision magnitude<\/p>\n priced above range \/ in range \/ below range<\/p>\n 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.<\/p>\n resolved listing date<\/p>\n resolved exchange<\/p>\n resolved offer price<\/p>\n resolved shares<\/p>\n resolved proceeds<\/p>\n latest terms snapshot<\/p>\n classification<\/p>\n consensus ticker<\/p>\n consensus listing fields<\/p>\n The API supports company lookups with includes such as trading start date<\/p>\n first close<\/p>\n 1D return<\/p>\n week-one close<\/p>\n week-one return<\/p>\n current performance<\/p>\n offer-to-first-close return<\/p>\n offer-to-week-one return<\/p>\n IPOGrid has outcome rows for first close, 1D return, week-one close, and post-listing performance.<\/p>\n gross proceeds by week<\/p>\n prospectus counts<\/p>\n final prospectus counts<\/p>\n first-day returns by sector<\/p>\n filing activity by form family<\/p>\n sector-level IPO volume<\/p>\n recent IPO temperature<\/p>\n 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.<\/p>\n Use an API key for the richer endpoints:<\/p>\n Find companies and include the useful joins:<\/p>\n Fetch company detail by ticker or CIK:<\/p>\n Pull recent final prospectus filings:<\/p>\n Pull recent outcomes:<\/p>\n Pull public articles without auth:<\/p>\n The public article feed works without authentication; deeper company, filing, and outcome data uses API key bearer auth.<\/p>\n A clean IPO backtest should freeze the cohort before looking at outcomes.<\/p>\n For example:<\/p>\n IPOGrid\u2019s 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.<\/p>\n A row in a modeling dataset might look like this:<\/p>\n That table can feed normal financial modeling workflows: screening, regression, ranking, clustering, risk controls, or event studies.<\/p>\n 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\u2019s freshness docs explicitly warn not to silently fill missing historical fields with today\u2019s values.<\/p>\n 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.<\/p>\n 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.<\/p>\n A few useful models you can build from this:<\/p>\n IPO readiness screen: find effective or recently amended operating IPOs with exchange listing signals and extracted terms.<\/p>\n Pricing-change model: compare initial range, revised range, final offer price, and sector conditions.<\/p>\n Day-one return model: join final prospectus terms to first close and sector-level IPO context.<\/p>\n Week-one fade model: compare first close to week-one close.<\/p>\n Filing-momentum model: count amendments, form changes, and final prospectus timing.<\/p>\n Sector heat model: use chart data to track issuance volume, proceeds, and first-day returns by sector.<\/p>\n 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.<\/p>\n<\/div>\n submitted by \/u\/ipogrid <\/a> What you can pull<\/h1>\n
Example feature families<\/h1>\n
Issuer identity features<\/h1>\n
Filing timeline features<\/h1>\n
Deal term features<\/h1>\n
Consensus \/ listing features<\/h1>\n
latest_terms<\/code>, classification<\/code>, consensus<\/code>, filings<\/code>, news<\/code>, and financial_snapshot<\/code>.<\/p>\nOutcome features<\/h1>\n
Market context features<\/h1>\n
Basic API calls<\/h1>\n
export IPOGRID_API_KEY=\"your_key_here\" <\/code><\/pre>\ncurl -H \"Authorization: Bearer $IPOGRID_API_KEY\" \"https:\/\/ipogrid.com\/api\/v1\/companies?scope=all&kind=operating&include=latest_terms,classification,consensus\" <\/code><\/pre>\ncurl -H \"Authorization: Bearer $IPOGRID_API_KEY\" \"https:\/\/ipogrid.com\/api\/v1\/companies\/spcx?include=filings,news,latest_terms,classification,consensus,financial_snapshot\" <\/code><\/pre>\ncurl -H \"Authorization: Bearer $IPOGRID_API_KEY\" \"https:\/\/ipogrid.com\/api\/v1\/filings?form_type=424B4&filing_date_from=2026-06-01&include=company,terms\" <\/code><\/pre>\ncurl -H \"Authorization: Bearer $IPOGRID_API_KEY\" \"https:\/\/ipogrid.com\/api\/v1\/outcomes?trading_start_date_from=2026-06-01&limit=100\" <\/code><\/pre>\ncurl \"https:\/\/ipogrid.com\/api\/v1\/articles?limit=30\" <\/code><\/pre>\nBacktest shape<\/h1>\n
\n
Example model table<\/h1>\n
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 <\/code><\/pre>\nCaveats<\/h1>\n
Practical use cases<\/h1>\n
[link]<\/a><\/span> [comments]<\/a><\/span><\/p>
