The Form 424B7 Files Dataset is a complete corpus of EDGAR submissions filed under Rule 424(b)(7) of the Securities Act of 1933 — prospectus supplements that name the selling security holders and amounts of securities those holders propose to sell, completing information omitted from an effective shelf registration in reliance on Rule 430B. Each record corresponds to one accession-numbered EDGAR filing, packaged as an accession-named folder inside a monthly ZIP container alongside a metadata.json descriptor and every document attached to the submission. The dataset is filed by the issuer named on the underlying registration statement (typically a Form S-3, F-3, or S-3ASR shelf), not by the selling holders themselves, and is event-driven rather than periodic. Coverage begins in September 1996, consistent with EDGAR's mandatory electronic filing of Securities Act submissions. The dataset is distributed in ZIP containers and contains TXT, JSON, HTML, and PDF files.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset captures every Form 424B7 prospectus supplement filed on EDGAR from September 1996 to the present. Form 424B7 is used to identify selling security holders and the amounts of securities those holders propose to sell when that information had previously been omitted from an effective shelf registration statement in reliance on Rule 430B. Functionally, the document re-opens an already-effective registration by naming the resale sellers, their pre- and post-offering ownership, and the size of the offering being made by each. It is not a standalone registration: it supplements and incorporates by reference the base prospectus and the prior registration statement, and it must be filed no later than the second business day following the earlier of the date of sale or first use.
Because Form 424B7 is a supplement to a shelf rather than a standalone offering document, its content is heavily structured around the selling-securityholder table and is comparatively narrow in scope versus a full prospectus or registration statement. Filings range from short one-document supplements that merely refresh the selling-stockholder roster to longer supplements that include a plan of distribution, risk factors, and an updated filing-fees exhibit. The dataset reproduces the textual EDGAR documents that constitute each 424B7 submission — the SGML-wrapped HTML prospectus supplement, any Inline XBRL filing-fees exhibit, any included PDF or supplemental text documents — together with a JSON descriptor summarizing the filing. File types in the dataset are TXT, JSON, HTML, and PDF; in practice modern records consist almost entirely of HTM/HTML documents plus the JSON descriptor.
A single record in the Form 424B7 Files Dataset is one complete EDGAR submission filed under Rule 424(b)(7), identified by its 18-digit EDGAR accession number. The record is materialized as an accession-named folder inside a monthly ZIP container, holding every document attached to that submission together with a metadata.json descriptor summarizing the filing. The unit of granularity is the filing as a whole, not the prospectus supplement document or any individual exhibit: the prospectus supplement, the filing-fees exhibit, and any other attachments are all bundled within the one record.
Each record consists of two layers:
metadata.json) capturing the filing-level facts EDGAR exposes in its submission header and document index: form type, accession number, filing time, links back to the SEC source, the registrant/filer entity block, and a manifest of every document attached to the submission..htm) and, when applicable, an Inline XBRL filing-fees exhibit (.htm). Each document is delivered in EDGAR's native SGML-wrapped form: a <DOCUMENT> envelope with <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> headers preceding the inner HTML or text body.The accession folder is named with the dash-stripped 18-digit accession number. Individual document filenames are passed through unchanged from the EDGAR submission, preserving filer-chosen naming conventions such as *_424b7.htm, *_ex107.htm, or *_exfilingfees.htm.
metadata.jsonA single JSON object summarizing one filing. The top-level fields describe the submission:
formType is fixed at "424B7" for every record in the dataset.accessionNo is the dashed EDGAR accession number (e.g., "0001104659-25-104968").filedAt is an ISO 8601 timestamp with timezone offset capturing EDGAR acceptance time.description carries EDGAR's human-readable form description, typically "Form 424B7 - Prospectus [Rule 424(b)(7)]".linkToFilingDetails, linkToTxt, linkToHtml, and linkToXbrl are direct URLs to the EDGAR filing-index page, the complete-submission text aggregate, the primary HTML document, and the XBRL instance respectively. linkToXbrl is frequently empty for 424B7 records because the only XBRL payload, when present, is the filing-fees exhibit.id is a 32-character hex identifier assigned by the data provider for stable referencing.Two array fields manifest the filing's documents:
documentFormatFiles lists every document attached to the EDGAR submission with sequence, size, documentUrl, description, and type. Type values include 424B7 for the primary supplement, EX-FILING FEES for the Rule 457 fees exhibit, GRAPHIC for image references, and the trailing complete-submission .txt aggregate. The sequence values mirror the filer-assigned ordering from the EDGAR submission.dataFiles enumerates XBRL/data sidecar files associated with the submission, typically the extracted XBRL XML for the Inline XBRL filing-fees exhibit.The entities array carries one object per party identified in the EDGAR header (issuer, filer, and any other roles). Per-entity fields include companyName (with a role suffix such as "(Filer)"), cik, irsNo, fileNo (the SEC file number tying the supplement back to the underlying registration statement, e.g., "333-290092"), filmNo, act (securities act number, typically "33"), type (the form type as it pertains to that entity), sic (SIC code with description), fiscalYearEnd (MMDD), stateOfIncorporation (two-letter code), and tickers (an array of associated trading symbols). The fileNo is load-bearing for 424B7 records because it is the canonical link from a supplement to the shelf registration statement it is updating.
A seriesAndClassesContractsInformation array is also present for series/class disclosures associated with investment companies; it is typically empty for 424B7 records.
The primary document is delivered as an SGML-wrapped HTML file. The outer wrapper carries <TYPE>424B7, <SEQUENCE>1, a <FILENAME> matching the in-folder filename, a <DESCRIPTION> of 424B7, and a <TEXT> block enclosing the HTML payload. Inside that payload the supplement typically contains, in order:
Preliminary 424B7 supplements (filed before final pricing or before a holder list is finalized) carry the standard preliminary-prospectus legend on the cover but are otherwise structurally identical.
When the supplement registers additional fee-bearing amounts or otherwise triggers Rule 457 fees disclosure, the filing includes an Inline XBRL filing-fees exhibit, typically named with an _ex107 or _exfilingfees suffix and described in documentFormatFiles as EX-FILING FEES. The document declares xmlns:ix, xmlns:dei, and xmlns:ffd namespaces. Identifying facts such as ffd:FormTp (the underlying form type, frequently S-3), ffd:SubmissnTp (424B7), ffd:RegnFileNb (the registration file number), dei:EntityCentralIndexKey, and dei:EntityRegistrantName are emitted within ix:hidden, while the visible body renders the structured filing-fees table required by Item 16(b) and Rule 457. Short prospectus-supplement updates that do not introduce new fee-bearing offerings often omit this exhibit entirely.
Image and graphic files (logos, signature graphics, charts) referenced by the prospectus appear as GRAPHIC entries in documentFormatFiles, but the image binaries themselves are excluded from the dataset. The complete-submission .txt aggregate is referenced via linkToTxt rather than reproduced in-folder in every case.
Image binaries (.jpg, .gif, and similar) referenced from within the prospectus are deliberately omitted; their existence remains discoverable through documentFormatFiles entries with type: "GRAPHIC", but the bytes are not included. The base prospectus and the underlying registration statement (Form S-3 or other) are not embedded in the record; they are incorporated by reference and must be retrieved separately using the fileNo (e.g., "333-XXXXXX") from entities[]. Other prospectus supplements filed against the same shelf are likewise separate records, each with its own accession number. Fairness opinions, consent letters, or Form 8-K disclosures cited by the supplement are not part of the 424B7 record.
The structure of 424B7 filings has evolved alongside several SEC rule changes that materially shape record content:
EX-FILING FEES document with the ffd namespace and structured tags; earlier records embed the fee table inline within the prospectus body in narrative form. This is the most visible structural change in the modern era of 424B7 filings.The format evolution mirrors EDGAR's broader trajectory:
.txt document. Tabular content, including the selling-stockholder table, was rendered in fixed-width ASCII..htm files inside the same SGML <DOCUMENT> wrapper. PDF copies are occasionally attached alongside the HTML primary.EX-FILING FEES document. The prospectus supplement itself does not carry XBRL tagging; only the filing-fees exhibit is tagged. The dataFiles array in metadata.json exposes the extracted XBRL XML sidecars when present.The SGML <DOCUMENT> wrapper around every primary document and exhibit is constant across the entire date range, regardless of whether the inner payload is ASCII text, HTML, or Inline XBRL.
<DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT>) precede the HTML body in every document file. Pipelines feeding documents into an HTML parser should strip or skip these header lines first; the inner <html> payload carries the prospectus narrative.entities[].fileNo field is the canonical link from a 424B7 record to the underlying registration statement. Multiple 424B7 filings may share the same fileNo over the life of a shelf, each updating or supplementing the selling-securityholder roster.424B7 document and no EX-FILING FEES exhibit, the supplement is generally a roster update or other non-fee-triggering revision of an existing offering rather than a new fee-bearing registration.424B7/A submissions, when used, fall outside this dataset's exact 424B7 form-type scope. The dataset captures records whose form type is exactly 424B7.Each Form 424B7 is a prospectus supplement filed by the issuer named on an effective Securities Act registration statement that previously relied on Rule 430B to omit information about selling security holders. The issuer is the filer of record on EDGAR; the selling security holders are the subjects of the disclosure, not the filers. The 424B7 is not a standalone registration: it completes a base prospectus by adding the identities of selling holders and the amounts of securities they intend to sell, information that Rule 430B permitted the issuer to leave blank when the registration statement went effective.
Rule 430B is only available to certain issuers and contexts, so the 424B7 filer pool is narrower than the broader 424(b) population. Typical filers include:
Issuers without an effective shelf, or whose registration did not rely on Rule 430B, do not file 424B7.
The filing is event-driven, not periodic. Under Rule 424(b)(7), the supplement must be filed no later than the second business day following the earlier of:
"First use" includes circulation to potential investors or dissemination by an underwriter, even before any sale. A single shelf can therefore generate many 424B7 filings over its life, each tied to a separate shelf takedown by a different holder or to additional securities for a previously identified holder. Filings cluster around secondary offerings, sponsor exits, lockup expirations, and conversions followed by registered resale.
The 424B7 sits in the Securities Act prospectus regime, not the Exchange Act periodic-reporting regime. Governing provisions:
By operation of Rule 430B, information added by a 424B7 is deemed part of the registration statement as of the date of first use, which is what makes the newly identified holder's resale a registered offering for Section 5 purposes.
The earliest records in this dataset begin in September 1996, consistent with EDGAR-wide mandatory electronic filing of Securities Act submissions phased in through May 1996. Pre-EDGAR paper supplements identifying selling holders are not included. The 424B7 designation predates the SEC's 2005 Securities Offering Reform, but its volume expanded materially afterward as WKSI automatic shelves and resale shelves became the dominant mechanism for registering secondary offerings.
Form 424B7 sits inside the Rule 424(b) family of prospectus filings under the Securities Act of 1933. Its closest neighbors are the other 424(b) sub-types, the shelf registration statements it supplements, and the ownership and insider-transaction regimes that touch the same selling-holder population. Each looks similar on the surface but is triggered by a different rule, fills in a different omission, and follows a different timing logic.
Each 424(b) variant maps to a specific omission or update trigger. The contrast with 424B7 is sharpest on what is being filled in and who is selling:
Form 424B7 is defined by a single, narrow Securities Act mechanism: a prospectus supplement under Rule 424(b)(7) that fills in selling-security-holder information permissibly omitted under Rule 430B from an effective shelf registration. That trigger distinguishes it from every other 424(b) sub-type (pricing, takedown terms, generic updates, continuous offerings), from the underlying shelves (which set capacity but rarely name resale sellers), from Form 144 (exempt, unregistered resales), and from 13D/13G and Section 16 (ownership and insider trades independent of any registered offering). It is the cleanest SEC source for identifying who is selling registered shares in secondary offerings, in what amounts, and on what timeline — a question no adjacent dataset answers directly.
Form 424B7 supplements name the selling security holders and share counts left blank under Rule 430B in an effective shelf. The corpus is narrow but read closely by a defined set of professional users.
Disclosure counsel use the dataset as a precedent library when drafting their own 424B7s. They focus on selling-holder tables, footnotes describing how shares were acquired (sponsor exits, PIPE conversions, warrant exercises, merger consideration), plan-of-distribution language, material-relationships disclosure, and incorporation-by-reference blocks. Output supports peer benchmarking on affiliate status, Rule 13d-3 beneficial-ownership computation, registration-rights triggers, and Rule 415 compliance.
Sell-side and buy-side analysts treat 424B7 filings as a leading indicator of secondary supply that pressures price without diluting the issuer. They watch holder identities, cumulative shares registered, timing relative to lockup expiration, and whether distribution will be an underwritten block or dribble-out. Inputs feed supply-overhang notes, post-IPO sponsor-exit models, and trade calendars.
ECM bankers study how sponsors, founders, and strategic holders monetize registered positions: syndicate structure, lockup carve-outs, block-trade and accelerated-bookbuild mechanics. M&A teams mine post-merger and de-SPAC 424B7s to confirm consideration and earn-out shares were properly registered and to track legacy-holder unwinds. Output supports pitch comps and registration-rights drafting in new deals.
Resale registration is the standard exit for privately placed securities tied to an effective shelf. Specialists trace the bridge from an originating 8-K to the matching 424B7, focusing on share counts (including shares underlying convertibles, warrants, and pre-funded warrants) and conversion mechanics. The corpus supports comparable-deal analysis and tracking when PIPE investors become eligible to sell.
Long-short and event desks monitor when sponsors, insiders, and affiliated funds register shares for resale. They key on holder identity and relationship to the issuer, pre- and post-offering ownership, and maximum offering size. Joined to Form 4 and 13D/G data, the dataset informs secondary-offering arbitrage, overhang shorts, and lockup-expiry trades.
Compliance officers verify that takedowns were filed within the two-business-day Rule 424(b)(7) window, that the cover correctly references the base prospectus, and that selling-holder disclosure satisfies the Rule 430B omission. They also confirm aggregate registered amounts have not exceeded shelf capacity. Workflow outputs include internal audits, deficiency-letter responses, and Form S-3 eligibility reviews.
Quant teams extract structured fields from selling-holder tables (pre-offering ownership, shares offered, post-offering ownership, percentage of class), filing date, and effective registration reference, then join to price, volume, and short-interest data. Output feeds supply-shock factors, lockup-release event studies, and execution algorithms for days around secondary events.
Governance analysts map the dispersion of concentrated holdings over time using the schedule of selling holders, footnoted ties to directors and officers, and cumulative effects across successive 424B7s. The corpus supports control-status assessments and longitudinal ownership-life-cycle studies of sponsor-backed and newly public issuers.
Engineering teams use the accession-level structure, JSON metadata, and HTML/TXT/PDF document set to build normalized selling-holder tables, takedown registries, and shelf-utilization dashboards. RAG and fine-tuning teams use the corpus to train and evaluate extraction of selling-holder schedules, plan-of-distribution language, and incorporation-by-reference chains on a narrow, tabular filing type.
In summary: lawyers draft these supplements; bankers and PIPE specialists structure the deals behind them; analysts, hedge funds, and quants price the resulting supply; compliance officers police filing mechanics; governance and data teams track ownership transitions. Each reads the same document for different fields.
Each use case below targets a specific section of the 424B7 record (selling-holder tables, plan-of-distribution language, the Rule 430B legend, file numbers, or filing timestamps) and supports a defined downstream workflow.
Parse metadata.json for filedAt and the entities[].fileNo linking each supplement to its underlying S-3/F-3 shelf, then extract the selling-securityholder table from the primary 424B7.htm document to capture per-holder shares offered. The output is a chronological calendar of registered secondary supply by issuer, used by event-driven desks and ECM analysts to anticipate block trades, dribble-out programs, and overhang pressure relative to lockup expirations and earnings windows.
Use the fileNo to group all 424B7 supplements against the same shelf, then mine the selling-holder footnotes for acquisition-history language ("acquired in connection with the merger," "issued upon conversion of the Series A Preferred," "purchased in the private placement on [date]"). Joining these footnotes to prior 8-K announcements produces a deal-by-deal trace from private placement or merger consideration through the matching resale registration, supporting comparable-deal benchmarking by PIPE specialists and de-SPAC counsel.
Securities counsel query the corpus for plan-of-distribution clauses (block trades, ATM, distributions to limited partners, hedging carve-outs, pledge mechanics) and for footnote conventions on Rule 13d-3 aggregation, voting/dispositive power, and material-relationships disclosure. The HTML primary document and its preserved heading structure feed a precedent retriever used during 424B7 drafting and registration-rights negotiation.
Compare the filedAt timestamp against the date of sale or first use referenced inside the supplement's cover and plan-of-distribution sections to verify each takedown was filed within the Rule 424(b)(7) two-business-day window. Cross-check the cover's Rule 430B legend, the base-prospectus reference, and the registered amount against the shelf's remaining capacity (aggregated from prior 424B7s sharing the same fileNo). The workflow drives internal audits, deficiency-letter responses, and S-3 eligibility reviews for issuers and underwriters.
Extract the structured fields from the selling-holder table (pre-offering beneficial ownership, shares offered, post-offering ownership, percentage of class) and the EX-FILING FEES Inline XBRL exhibit (ffd:RegnFileNb, registered amount, fee basis) into a panel keyed by issuer CIK and accession number. Joined to price, volume, short-interest, and Form 4 trade data, this panel feeds supply-overhang factors, secondary-offering event studies, and execution algorithms for the days surrounding registered resale events.
Concatenate selling-holder tables across successive 424B7 filings sharing the same fileNo to reconstruct how sponsor funds, founders, and strategic holders draw down concentrated positions over the life of a shelf. Footnoted director and officer affiliations connect named holders to governance roles, supporting control-status assessments, sponsor-exit timelines, and ownership-life-cycle studies for newly public and sponsor-backed issuers.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-424b7-files.json
This endpoint returns dataset-level metadata (name, description, last update timestamp, earliest sample date, total records, total size, form types, container format, and file types), the download URL for the full dataset archive, and the list of individual container files with per-container metadata such as size, record count, last updated timestamp, and download URL. Use it to monitor which containers were touched in the most recent refresh run and decide which files to pull on a given day. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-693a-b5e3-94988da2e26f",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-424b7-files.zip",
4
"name": "Form 424B7 Files Dataset",
5
"description": "Form 424B7 filings contain prospectus supplements filed pursuant to Rule 424(b)(7) under the Securities Act of 1933.",
6
"updatedAt": "2026-04-28T02:57:29.817Z",
7
"earliestSampleDate": "1996-09-01",
8
"totalRecords": 5434,
9
"totalSize": 206705934,
10
"formTypes": ["424B7"],
11
"containerFormat": "ZIP",
12
"fileTypes": ["TXT", "JSON", "HTML", "PDF"],
13
"containers": [
14
{
15
"downloadUrl": "https://api.sec-api.io/datasets/form-424b7-files/2026/2026-04.zip",
16
"key": "2026/2026-04.zip",
17
"size": 4185762,
18
"records": 38,
19
"updatedAt": "2026-04-28T02:57:29.817Z"
20
}
21
]
22
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-424b7-files.zip?token=YOUR_API_KEY
Returns the complete dataset as a single ZIP archive covering all 424B7 filings from the earliest sample date (1996-09-01) onward. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-424b7-files/2026/2026-04.zip?token=YOUR_API_KEY
Downloads one individual monthly container (ZIP) instead of the full dataset, which is useful for incremental updates. Container paths are listed under containers[].downloadUrl in the dataset index. This endpoint requires an API key.
One record is a single complete EDGAR submission filed under Rule 424(b)(7), identified by its 18-digit accession number. It is materialized as an accession-named folder containing a metadata.json descriptor and every document attached to the submission — typically the SGML-wrapped HTML prospectus supplement and, when applicable, an Inline XBRL filing-fees exhibit.
The dataset covers Form 424B7, a prospectus supplement filed under Rule 424(b)(7) of the Securities Act of 1933. It is used to identify selling security holders and the amounts of securities those holders propose to sell when that information had previously been omitted from an effective shelf registration statement in reliance on Rule 430B.
The issuer named on the underlying registration statement files the 424B7 — not the selling security holders themselves. Typical filers are domestic registrants with an effective Form S-3 shelf, well-known seasoned issuers (WKSIs) using S-3ASR automatic shelves, foreign private issuers with effective Form F-3 shelves, and, less commonly, certain S-1 registrants relying on Rule 430B(a)(2)(ii).
Filings are event-driven. Under Rule 424(b)(7), the supplement must be filed no later than the second business day following the earlier of the first sale of registered securities by the selling holder being added or updated, or the first use of the prospectus supplement that identifies that holder.
424B7 is uniquely triggered by Rule 430B omission of selling-holder information, so it is filed by the issuer to enable resales by existing holders. 424B1/B4 fill in Rule 430A pricing for primary offerings, 424B2/B5 are primary shelf takedown supplements, and 424B3 is the catch-all for residual substantive changes. The presence of a 424B7 implies an underlying S-3, F-3, or S-3ASR shelf, not an S-1.
The dataset begins on 1996-09-01, consistent with EDGAR's mandatory electronic filing of Securities Act submissions, and continues through the present with monthly container updates. It is distributed as ZIP containers and contains TXT, JSON, HTML, and PDF files, with modern records dominated by HTM/HTML documents plus the JSON descriptor.
Image binaries (.jpg, .gif, and similar) referenced from within the prospectus are deliberately omitted, though their existence remains discoverable through documentFormatFiles entries with type: "GRAPHIC". The base prospectus and the underlying registration statement (Form S-3 or other) are not embedded; they are incorporated by reference and must be retrieved separately using the fileNo from entities[]. Other prospectus supplements filed against the same shelf are likewise separate records.