Registration Statement & Prospectus Data API

Search the /form-s1-424b4 endpoint and filter on the issuer's trading symbol, which is stored at the top level of each item (ticker) and also on each offered security (tickers.ticker). For example, to retrieve the offering data for a company that went public under the symbol BABA, filter where ticker equals BABA. Each matching item is the extracted structured data from one registration statement or prospectus, including the offering amounts (publicOfferingPrice, underwritingDiscount, proceedsBeforeExpenses), the securities offered (securities), and the deal participants (underwriters, lawFirms, auditors).

If you only know the company name rather than its symbol, you can also filter on the issuer name (entityName). Note that a company may have several filings under one ticker — an original Form S-1, one or more amended S-1/A versions, and a final 424B4 prospectus — so a ticker search typically returns the full set of filings for that offering rather than a single document.

Search the /form-s1-424b4 endpoint and filter on the issuer's Central Index Key, which appears on every item as cik. The CIK is the SEC's permanent identifier for a company and is stored with leading zeros removed, for example 1318605 for Tesla. Filtering where cik equals the company's CIK returns every Form S-1, S-1/A, F-1, F-1/A, S-11, S-11/A registration statement and every 424B4 prospectus on file for that issuer.

Results default to descending order by filing date (filedAt), so the most recent filings appear first. To walk through a company's offering history chronologically, sort ascending by filedAt instead. If you have a ticker rather than a CIK, the /mapping-api endpoint resolves a trading symbol to its CIK.

Search the /form-s1-424b4 endpoint and filter on the accession number, which is stored on every item as accessionNo. The accession number is the SEC's unique identifier for an individual filing, formatted with dashes such as 0001628280-24-023559. Filtering where accessionNo equals that value returns the single extracted record for that exact filing.

Because an accession number identifies one specific document, this search returns at most one item, and the total.value field of the response will be 1 when the filing exists in the dataset.

Search the /form-s1-424b4 endpoint and filter on the filing acceptance date (filedAt), which records when SEC EDGAR accepted the filing for processing. To capture an entire calendar year such as 2022, the value of filedAt should fall between 2022-01-01 and 2022-12-31, inclusive of both endpoints.

A full year of registration statements and prospectuses can exceed the 10,000-result cap on a single search. If the response shows total.value at or above 10,000, narrow the filedAt window to one month at a time and iterate across the twelve months to collect every result.

Search the /form-s1-424b4 endpoint and filter on the EDGAR form type, stored on every item as formType. An original registration statement carries formType of S-1, an amended registration statement carries S-1/A (the /A suffix marks an amendment), and the final prospectus that contains confirmed pricing carries 424B4. Filtering formType to a single one of these values isolates that stage of the offering process.

A typical IPO produces all three over time: the company files an S-1, revises it through one or more S-1/A amendments, and concludes with a 424B4 once the deal is priced. To compare stages for one company, combine a formType filter with the issuer's cik. Foreign issuers use F-1 and F-1/A instead of S-1 and S-1/A, and real estate issuers use S-11 and S-11/A.

Search the /form-s1-424b4 endpoint and filter the form type (formType) to 424B4. A 424B4 is the final prospectus filed after a deal is priced, and unlike preliminary S-1 registration statements it typically includes confirmed pricing in the offering amount objects (publicOfferingPrice, underwritingDiscount, proceedsBeforeExpenses).

While most S-1 filings leave the pricing objects empty, 424B4 prospectuses generally populate the per-share and total figures, such as publicOfferingPrice.perShare and publicOfferingPrice.total. Restricting the search to formType of 424B4 is the most direct way to keep only offerings with finalized pricing data.

Search the /form-s1-424b4 endpoint and use the form type field (formType) to exclude the amendment values. Amended registration statements carry the /A suffix — S-1/A, F-1/A, and S-11/A — so a search that requires formType to not equal S-1/A removes the amended S-1 filings and leaves the original S-1 registration statements.

To keep only original registration statements across all categories, exclude S-1/A, F-1/A, and S-11/A together, or, more directly, restrict formType to the original values S-1, F-1, and S-11. Excluding amendments is useful when you want one record per offering rather than every successive revision.

Search the /form-s1-424b4 endpoint and sort the results by the total public offering price (publicOfferingPrice.total) in descending order, which places the biggest deals first. The publicOfferingPrice.total field holds the aggregate dollar amount of the offering as a number, for example 1365000000 for a $1.365 billion deal.

Because many preliminary S-1 registration statements leave the pricing objects empty, restrict the search to finalized prospectuses by filtering formType to 424B4 so that every ranked result has a populated total. Sorting then returns the priced offerings ordered from largest to smallest deal size.

Search the /form-s1-424b4 endpoint and filter on the total public offering price (publicOfferingPrice.total), which stores the aggregate deal size as a number. To find offerings of $100 million or more, the value of publicOfferingPrice.total should be greater than or equal to 100000000.

Since preliminary S-1 registration statements often leave publicOfferingPrice empty, pair the amount filter with a formType of 424B4 to limit results to finalized prospectuses that carry confirmed pricing. Sorting by publicOfferingPrice.total in descending order then ranks the qualifying deals from largest to smallest.

Search the /form-s1-424b4 endpoint and filter on the underwriter name, stored in the underwriters array as underwriters.name. Each item in underwriters is one bank involved in the offering — the first entry is typically the lead underwriter and the rest are co-managers — so a filter where underwriters.name matches a firm such as Goldman Sachs returns every deal that bank participated in regardless of its role.

The array does not distinguish lead from co-manager beyond ordering, so a name filter captures both. To rank the matching deals by size, sort by publicOfferingPrice.total in descending order. Note that some S-1 registration statements have no underwriters listed yet; the names may appear later in an S-1/A amendment as they become known.

Search the /form-s1-424b4 endpoint and filter on the law firm name, stored in the law firms array as lawFirms.name. Each item in lawFirms represents one legal counsel involved in the offering, with the firm's name (lawFirms.name) and its location (lawFirms.location). Filtering where lawFirms.name matches a firm such as Wilson Sonsini Goodrich & Rosati returns every offering that firm advised on.

A single filing often lists several law firms, since both issuer's counsel and underwriters' counsel are disclosed, so a name match identifies any deal the firm was named on. To rank the matching offerings by deal size, sort by publicOfferingPrice.total in descending order.

Search the /form-s1-424b4 endpoint and filter on the auditor name, stored in the auditors array as auditors.name. Each item in auditors is one accounting firm that audited the issuer's financial statements for the offering, for example Deloitte & Touche LLP or Ernst & Young LLP. Filtering where auditors.name matches a firm returns every offering that firm audited.

Some filings list more than one auditor, for instance when a recently acquired business was audited separately, so a name match captures any offering where the firm is named. Pair the filter with a formType value or a filedAt date range to narrow the results to a particular offering stage or time period.

Search the /form-s1-424b4 endpoint and filter on the law firm location, stored in the law firms array as lawFirms.location. Each law firm entry carries both a name (lawFirms.name) and a location string (lawFirms.location), such as Cayman Islands, New York, United States, or California, USA. Filtering where lawFirms.location matches the jurisdiction you want returns offerings where at least one named law firm is based there.

The location strings are not standardized to a fixed list, so a jurisdiction may appear with slight wording variations; matching on the jurisdiction term such as Cayman Islands captures the relevant filings. Cayman Islands counsel commonly appears on offerings by offshore-incorporated issuers, including many SPACs.

Search the /form-s1-424b4 endpoint and filter on the total employee count, stored on the employees object as employees.total. This field holds the total headcount the issuer disclosed in the filing as a number, for example 10800. To screen for larger companies, the value of employees.total should be greater than the threshold you choose, such as greater than 1000.

The filing may also break headcount down by business unit (employees.perDivision) and by geographic region (employees.perRegion), and may record the date the count was measured (employees.asOfDate). Note that not every filing discloses an employee count, so filings with an empty employees.total will not appear in a numeric range search.

Search the /form-s1-424b4 endpoint and filter on the age of management team members, stored on each person in the management array as management.age. Each item in management describes one executive or director with a name (management.name), an age (management.age), and a position (management.position). To find filings where at least one team member falls in a given age band, the value of management.age should fall between the lower and upper bounds, for example between 70 and 100.

Because the filter matches if any single member's age is in range, the result set is offerings whose disclosed management includes someone of that age. To bring the oldest team members to the top, sort by management.age in descending order. Excluding amended filings by setting formType to not equal S-1/A avoids counting the same offering's roster multiple times.

Search the /form-s1-424b4 endpoint for the company by its cik or ticker, and read the management array on the returned item. Each entry in management is one member of the management team, with the person's name (management.name), age (management.age), and position (management.position).

The position text is taken directly from the filing and is not standardized — the same role may appear as CEO, Chief Executive Officer, or President depending on the company. Ages are present when the filing discloses them and may be empty otherwise. Reviewing the management array of a single filing gives the full disclosed roster of executives and directors for that offering.

Search the /form-s1-424b4 endpoint and filter on the security type so that the offered securities include a unit. Each offered security appears in the tickers array with a type (tickers.type), and SPAC unit IPOs carry a tickers.type of Units alongside a separate Warrants entry, since the unit bundles a share and a warrant. The securities array also describes these in plain text, for example tickers.type of Units with a securities.name such as 25,000,000 Units Each Consisting of One Class A ordinary share and One-Third of One Redeemable Warrant.

Filtering where tickers.type equals Units isolates offerings structured as unit IPOs, which are characteristic of blank-check shell companies. To confirm the warrant component, look for a Warrants value in tickers.type on the same filing, and the bundle description in securities.name.

Search the /form-s1-424b4 endpoint and filter on the security description, stored as securities.name. Each entry in the securities array names a security being offered, and debt offerings describe notes or bonds in that text, for example 600,000,000 8.75% Senior Notes due 2019 or a convertible notes description. Filtering where securities.name contains terms such as Notes or Bonds surfaces debt offerings rather than common stock offerings.

Because securities.name is free-text extracted from the filing, debt instruments appear with varied wording — senior notes, subordinated notes, convertible notes, debentures — so matching on the relevant term captures the variations. The dataset includes registration statements for fixed-income and convertible securities alongside equity offerings.

Search the /form-s1-424b4 endpoint using both the security type and the security description. The security type on each ticker entry (tickers.type) carries a value of Warrants when warrants are listed, and the plain-text security descriptions (securities.name) name them explicitly, for example 1,358,350 Pre-Funded Warrants to Purchase 1,358,350 Common Shares. Filtering where tickers.type equals Warrants, or where securities.name contains Warrants or Pre-Funded Warrants, surfaces these offerings.

A filing that bundles warrants with common stock typically shows both a Common Stock and a Warrants entry in tickers.type, and the securities array describes each component. Pre-funded warrants in particular are identified through the securities.name text since they share the Warrants type.

Search the /form-s1-424b4 endpoint and filter on the security type and description. The security type on each ticker entry (tickers.type) records the class of security, and the plain-text descriptions in the securities array (securities.name) spell it out, for example 250,000 Shares of Series 2 Redeemable Preferred Stock. Filtering where tickers.type or securities.name contains Preferred Stock isolates preferred stock offerings from common stock offerings.

Because preferred stock is often issued in named series, the securities.name text frequently includes a series designation. Matching on the term Preferred in securities.name captures these variants regardless of the series label.

Search the /form-s1-424b4 endpoint for the offering, then read the exchange field on each offered security in the tickers array (tickers.exchange). Each entry in tickers describes one security with its symbol (tickers.ticker), its type (tickers.type), and the exchange it trades on or is being listed on (tickers.exchange), for example NASDAQ, NYSE, or American Stock Exchange.

If an offering includes several securities — such as units, ordinary shares, and warrants in a SPAC IPO — each appears as its own entry in tickers with its own tickers.exchange value. You can also filter directly on tickers.exchange to find all offerings being listed on a particular exchange.

Search the /form-s1-424b4 endpoint and filter the form type (formType) to the foreign-issuer registration values. Foreign private issuers register their offerings on Form F-1, the foreign equivalent of the domestic Form S-1, with amended versions carrying the F-1/A value. Filtering formType to F-1 returns original foreign registration statements, and F-1/A returns the amended versions.

To capture both the original and amended foreign filings together, include F-1 and F-1/A. The dataset covers F-1 and F-1/A registration statements alongside the domestic S-1, S-11, and 424B4 forms.

Search the /form-s1-424b4 endpoint and filter the form type (formType) to the real estate registration values. Real estate companies and real estate investment trusts register their securities offerings on Form S-11, the specialized registration form for real estate issuers, with amendments carrying the S-11/A value. Filtering formType to S-11 returns original real estate registration statements, and S-11/A returns the amended versions.

To retrieve both original and amended real estate filings together, include S-11 and S-11/A. The dataset covers S-11 and S-11/A registration statements alongside the S-1, F-1, and 424B4 forms.

Search the /form-s1-424b4 endpoint and retrieve the two total amounts from the offering: the total underwriting discount (underwritingDiscount.total) and the total public offering price (publicOfferingPrice.total). The underwriting fee as a percentage of the deal is the underwriting discount total divided by the public offering price total. For an offering with underwritingDiscount.total of 13230000 and publicOfferingPrice.total of 189000000, the fee works out to about 7 percent.

Both totals are most reliably populated on finalized prospectuses, so restrict the search to a formType of 424B4, where the pricing objects are typically complete. The endpoint returns the figures; the percentage itself is computed from the two total values after retrieval.

Search the /form-s1-424b4 endpoint and read the proceeds before expenses object, which records the amount the issuer receives after the underwriting discount is deducted from the public offering price. The total net amount is stored as proceedsBeforeExpenses.total, with a formatted string in proceedsBeforeExpenses.totalText and the corresponding per-share figure in proceedsBeforeExpenses.perShare.

This figure is the public offering price minus the underwriting discount — for an offering with a publicOfferingPrice.total of 189000000 and an underwritingDiscount.total of 13230000, proceedsBeforeExpenses.total is 175770000. It is labelled "before expenses" because it does not yet account for the offering's other costs such as legal and accounting fees. The proceeds object is generally populated on finalized 424B4 prospectuses and often empty on preliminary S-1 registration statements.

Search the /form-s1-424b4 endpoint and read the per-share value on the public offering price object. The numeric per-share price is stored as publicOfferingPrice.perShare, for example 18 for an offering priced at $18.00 a share, and the formatted string is in publicOfferingPrice.perShareText, for example $18.00.

The perShareText field is worth checking because it carries the currency symbol — most offerings are priced in US dollars, but in rare cases the price is in another currency, which perShareText makes explicit (for example €10.00). Per-share pricing is generally present on finalized 424B4 prospectuses and often absent on preliminary S-1 filings, so restrict the search to a formType of 424B4 when you need a populated price.

When searching the /form-s1-424b4 endpoint, treat the pricing objects — publicOfferingPrice, underwritingDiscount, and proceedsBeforeExpenses — as optional on early-stage filings. Original Form S-1 registration statements are frequently filed before a deal is priced, so these objects are commonly empty, while final 424B4 prospectuses typically carry complete per-share and total figures.

To work only with offerings that have confirmed pricing, filter the form type (formType) to 424B4, or require a numeric condition on a pricing field such as publicOfferingPrice.total being greater than 0, which excludes filings where the field is absent. If you need the full population including unpriced registration statements, search without a pricing filter and handle empty publicOfferingPrice objects in your own processing.

Search the /form-s1-424b4 endpoint and retrieve all of one company's filings by filtering on its cik, then compare the underwriters and lawFirms arrays across the different formType values. The original S-1 registration statement is often filed before underwriters are confirmed, so its underwriters array may be empty or short, while later S-1/A amendments add the underwriter names (underwriters.name) as they become known. The lawFirms array can similarly grow across amendments.

Sort the company's filings ascending by filedAt to see them in chronological order, then compare the length and contents of underwriters and lawFirms from the S-1 through each S-1/A. The difference in array entries between successive filings shows which deal participants were added or changed during the amendment process.

The /form-s1-424b4 endpoint returns at most 50 items per search, controlled by the size parameter, which defaults to 50 and cannot be set higher. To collect more than 50 results, page through them with the from parameter, which sets the starting offset: request the first page with from at 0, then 50, then 100, and so on, advancing by the page size each time until no further results come back.

The total.value field in the response tells you how many filings match the search overall, so you know how many pages to retrieve. The from offset can go up to 10,000, which is also the maximum number of results a single search will return.

The /form-s1-424b4 endpoint returns at most 10,000 results for any one search, so a query whose total.value reaches or exceeds 10,000 cannot be fully paged through as a single search. To collect every result, split the search into smaller windows using the filing date (filedAt) and process each window separately.

A practical approach is to constrain filedAt to one month or one year at a time — for example restrict filedAt to fall between 2023-01-01 and 2023-01-31, page through that month by advancing from in steps of 50 until exhausted, then repeat for the next month. Choose a window small enough that each slice stays under the 10,000-result cap, and iterate across all windows to cover the full search universe.