Form POS462C Files Dataset

The Form POS462C Files Dataset is a collection of EDGAR submissions of Form POS462C — the post-effective amendment to a Securities Act of 1933 registration statement that becomes effective immediately on filing under Rule 462(c). Each record is a single accession folder bundling the primary amendment document, its text-bearing exhibits, and a structured metadata.json manifest. The underlying form is filed by the issuer that originally registered the securities — typically on Form S-1, F-1, S-3, F-3, or S-11 — once the offering has been priced and the previously omitted Rule 430A pricing terms (public offering price, underwriting discounts and commissions, proceeds, and any price-derived figures) are folded into the registration statement. The dataset covers all Form POS462C filings submitted to EDGAR from June 1996 forward, distributed as monthly ZIP containers with JSON, HTML, and TXT file types.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset assembles every Form POS462C filing on EDGAR into a uniform, accession-level record set. Form POS462C is the EDGAR designation for a post-effective amendment to a registration statement that becomes effective immediately upon filing under Rule 462(c) of the Securities Act of 1933. Rule 462(c) is a narrow procedural mechanism permitting a post-effective amendment to take effect at the moment of filing, on the condition that the amended prospectus introduces no substantive changes from, or additions to, the previously effective prospectus other than information relating to the public offering price that had been omitted from the earlier prospectus in reliance on Rule 430A. The form is consequently used to lock in price-related terms — public offering price, underwriting discounts and commissions, proceeds to the issuer, aggregate offering amounts, and any registration-fee recalculations — for a registration statement that is otherwise already effective under the underlying form (most commonly Form S-1, F-1, S-3, or F-3).

Because POS462C is a post-effective amendment to an existing registration statement, the substantive content is the amended prospectus rather than a stand-alone disclosure document. The filing inherits the registrant identification, registration file number (the 333-… series), and offering structure of the underlying registration statement, and updates only the previously omitted Rule 430A pricing terms together with any directly consequential figures (registration fee table, capitalization, dilution, use of proceeds totals, plan of distribution arithmetic).

The dataset covers all Form POS462C filings submitted to EDGAR from June 1996 to the most recent refresh. Records are grouped into monthly ZIP containers, and each accession folder contains a JSON manifest plus the SGML-wrapped HTML documents that constituted the original submission. Image attachments and the wrapper complete-submission TXT envelope are referenced in the manifest but not duplicated into the bundle.

Content Structure of a Single Record

What one record represents

One record in the Form POS462C Files Dataset is a single EDGAR submission of Form POS462C, represented as a self-contained accession folder. The folder is keyed by the 18-digit unhyphenated SEC accession number and holds the textual documents that constituted the original submission, together with a metadata.json manifest that describes the filing at the accession level. Records are grouped into monthly ZIP containers under the layout <YYYY-MM>/<accessionNoDigits>/<files>, where each monthly archive aggregates every accession whose filing date falls in that calendar month. The hyphenated form of the accession number (e.g. 0001213900-25-107462) is preserved inside the manifest, while the folder name uses the digits-only form (e.g. 000121390025107462).

A record corresponds one-to-one with an EDGAR accession, not with an individual exhibit, page, or document. The record bundles the primary post-effective amendment document, every text-bearing exhibit attached to the submission, and the structured manifest that ties the filing to the registrant, the underlying registration statement being amended, and the position of each document within the original SGML submission.

Two structural layers of a record

A single record contains two structurally distinct layers:

1. A JSON manifest (metadata.json) that describes the filing at the accession level, enumerates every document originally part of the EDGAR submission, and carries the entity-level identification of the registrant.
2. A set of EDGAR document files, each wrapped in the standard SGML <DOCUMENT> envelope around an embedded HTML payload, representing the primary POS462C document and its exhibits.

The two layers are linked by sequence numbers: each document's <SEQUENCE> value in its SGML header matches an entry in documentFormatFiles[] of metadata.json, so the manifest functions as an authoritative table of contents for the documents present in the folder.

metadata.json structure

The manifest sits at the root of the accession folder and is present for every record. It carries the following fields:

• formType — fixed at POS462C for this dataset.
• accessionNo — the SEC accession number in hyphenated form (NNNNNNNNNN-YY-NNNNNN).
• effectivenessDate — the date the post-effective amendment became effective, which under Rule 462(c) coincides with the filing date.
• filedAt — the ISO-8601 filing timestamp with timezone offset.
• description — the human-readable form description, e.g. Form POS462C - Post-effective amendment to registration statement [Rule 462(c)].
• linkToFilingDetails — URL to the primary document on EDGAR.
• linkToTxt — URL to the full SGML "complete submission" text file on EDGAR.
• linkToHtml — URL to the EDGAR filing index page (-index.htm).
• linkToXbrl — URL to an XBRL instance; empty for POS462C, which does not carry inline XBRL.
• id — a 32-character hex identifier unique per filing.
• documentFormatFiles[] — an array of per-document descriptors covering every file in the original EDGAR submission, including image attachments and the wrapper complete-submission .txt, even though those are not extracted into the bundle. Each element carries sequence (string; the trailing complete-submission entry uses a single space), size (string, bytes), documentUrl (absolute EDGAR URL), description (free-form filer-supplied caption, possibly truncated), and type (the EDGAR document type such as POS462C, EX-5.1, EX-23.1, EX-23.2, GRAPHIC).
• dataFiles[] — a parallel array reserved for XBRL/data files; empty for POS462C.
• seriesAndClassesContractsInformation[] — investment-company series and class data; empty for typical operating-company POS462C filings.
• entities[] — one entry per filer/registrant. Each entry carries companyName (often suffixed by a role marker such as (Filer)), cik, type (the filer's role/form code), act (33 for Securities Act filings), fileNo (the underlying 333-… registration file number that uniquely identifies the registration statement being amended), irsNo, stateOfIncorporation (EDGAR's two-character code, e.g. E9 for the Cayman Islands), fiscalYearEnd (MMDD), sic (Standard Industrial Classification code and label), filmNo, and tickers[].

The entities[] array is the canonical place to retrieve issuer identification (CIK, legal name, jurisdiction, SIC, ticker), and entities[*].fileNo is the join key back to the registration statement being amended — the natural foreign key linking a POS462C record to the prior S-1, F-1, S-3, F-3, or other registration statement and its amendment chain.

Document files

Every non-metadata file in the accession folder is an EDGAR document wrapped in the standard SGML <DOCUMENT> envelope around an embedded HTML payload. The envelope opens with <DOCUMENT> and lists <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> lines, followed by <TEXT> and the HTML body, and closes with </TEXT></DOCUMENT>. The header lines preserve the filer-declared document type, the position of the document inside the original submission, the original on-disk filename, and any human-readable caption supplied by the filer.

Primary document

The primary document carries <TYPE>POS462C and <SEQUENCE>1. Its HTML payload is the amended prospectus / post-effective amendment, reflecting the final Rule 430A pricing information that triggered the amendment. The body typically includes, in narrative and tabular form:

• A cover page identifying the registrant, the underlying registration statement number, and the amendment number relative to the original registration statement (e.g. "Post-Effective Amendment No. 2 to Form F-1").
• The Calculation of Registration Fee table, recomputed against the now-finalized aggregate offering price and reconciled to fees previously paid.
• Prospectus front matter — offering summary, the offering box (price, shares offered, underwriting discounts and commissions, proceeds), risk factor cross-reference, and use of proceeds.
• Capitalization and dilution tables that mechanically depend on the finalized price.
• Plan of Distribution / underwriting section, updated for the final price terms, allotment options, stabilization disclosures, and the list of underwriters or selling agents.
• Any prospectus sections whose figures are derived from the price (e.g. selling-stockholder proceeds, lock-up references that quote the offering price, exchange listing disclosures referencing the trading price).

Because Rule 462(c) prohibits substantive changes beyond pricing, the bulk of the prospectus body is identical to the previously effective version, with the differences concentrated in the price-dependent sections and the fee table.

Exhibits

Exhibits follow the primary document and use the same SGML wrapper, each with its own <TYPE>, <SEQUENCE>, and <FILENAME> and an HTML payload appropriate to the exhibit's role. Typical exhibit types observed for POS462C filings include:

• EX-5.1 — opinion of counsel on the legality and validity of the securities being registered, often re-issued or reaffirmed in connection with the post-effective amendment and addressed to the issuer's board or to the underwriters.
• EX-23.1, EX-23.2, EX-23.3, EX-23.4 — consents of independent registered public accounting firms, named experts, and counsel, refiled to consent to the continued use of their names and reports in the post-effective amendment and the related prospectus.

Other exhibit types permitted by the underlying registration form may also appear when the issuer chooses to refile or update them concurrently with the post-effective amendment (for example, an updated form of underwriting agreement, lock-up agreement, or tax opinion).

Included content

For each accession, the dataset bundles:

• metadata.json — the manifest described above.
• The primary POS462C document as an SGML-wrapped .htm file.
• Every text-bearing exhibit (legal opinions, consents, and any other non-image exhibit materials) as SGML-wrapped .htm files.

The file-types found in the dataset are JSON (the manifest), HTML/HTM (the primary document and exhibits), and TXT (referenced in the manifest as the EDGAR complete-submission SGML envelope and reflected in the dataset-level file-type vocabulary).

Excluded content

Image attachments referenced by the original EDGAR submission — typically GRAPHIC entries in documentFormatFiles[] such as logo files, charts embedded in the prospectus, scanned signatures, and figure JPEGs/GIFs — are deliberately omitted from the bundled record. Their descriptors remain visible in the manifest with their original sequence, size, and documentUrl, so a consumer can fetch them from EDGAR directly when needed, but the binary image bytes themselves are not packaged into the ZIP. The wrapper complete-submission .txt enumerated in the manifest is similarly not duplicated in the folder; only linkToTxt points to it. No XBRL instance documents or financial data files are present, since POS462C filings do not carry inline XBRL.

Notes on structure and interpretation

• The record unit is the accession folder, not the document. A POS462C filing with five exhibits produces one record consisting of one folder, one metadata.json, and six SGML-wrapped .htm documents.
• The <SEQUENCE> values inside the SGML envelopes correspond to documentFormatFiles[].sequence in the manifest, allowing the metadata to act as a deterministic table of contents and a deterministic mapping between filer-declared types and on-disk filenames.
• The folder name is the 18-digit unhyphenated accession number; the hyphenated form lives only in metadata.accessionNo. Joining records to other SEC datasets typically requires the hyphenated form.
• entities[].fileNo carries the 333-… registration file number of the registration statement being amended; this is the natural join key to the underlying S-1, F-1, S-3, or F-3 filing and to any prior 424B-series prospectus supplements in the same offering.
• Because Rule 462(c) constrains the amendment to pricing-related changes, the substantive content of the prospectus body is largely a republication of the previously effective prospectus with finalized Rule 430A figures inserted. Diff-style comparisons against the immediately preceding prospectus (typically the most recent 424B filing or the underlying registration statement) tend to isolate the price-dependent paragraphs and the recomputed fee table.
• Filer-supplied descriptions in documentFormatFiles[].description are free-form, sometimes truncated, and inconsistently capitalized; they are useful as hints but should not be treated as a controlled vocabulary. The type field is the controlled label.
• Form POS462C has been filed exclusively in HTML wrapped in the SGML envelope across the period covered by this dataset, so there is no separate ASCII-only or XBRL era to account for. linkToXbrl is consistently empty.
• Although Rule 462(c) makes the amendment effective on filing, effectivenessDate and filedAt carry distinct semantics in the manifest: effectivenessDate is a calendar date, while filedAt is a full ISO-8601 timestamp with timezone, useful for ordering filings made on the same business day.

Who Files or Publishes This Dataset, and When

Who files the record

Each Form POS462C is a post-effective amendment to a Securities Act of 1933 registration statement, filed by the same issuer that originally registered the securities. The filer is the registrant on the underlying form (typically S-1, S-3, S-11, F-1, or F-3) whose effective prospectus omitted price-dependent information in reliance on Rule 430A. The amendment is filed under the original registration statement file number and signed under the signature requirements of that underlying form.

No new or third-party filer is involved. The producing party is always an issuer with an already-effective Securities Act registration statement that needs to complete the prospectus by adding final pricing terms.

Filing population

The eligible population is defined by three conditions, all of which must hold:

• The filer is a Securities Act registrant whose registration statement is already effective (including by operation of Rule 430A).
• The previously effective prospectus omitted price-dependent information under Rule 430A. Such information includes the public offering price, underwriting discounts and commissions, syndicate composition, proceeds to the issuer, and price-derived conversion ratios.
• The registrant elects to fold the final pricing information into the registration statement itself via a Rule 462(c) post-effective amendment, with immediate effectiveness on filing.

In practice the population skews toward issuers in firm-commitment underwritten IPOs and follow-on offerings priced after Commission effectiveness. It includes domestic operating company registrants and foreign private issuers using F-series forms.

Triggering event

A POS462C is triggered by a single event: the registrant has determined the final price-related terms of the offering that were omitted at original effectiveness and is incorporating them into the registration statement by post-effective amendment. The filing exists for that purpose alone.

The Rule 462(c) procedure imposes one substantive constraint: the amended prospectus must contain no substantive changes from the previously effective prospectus other than the Rule 430A pricing information. Any change beyond pricing-derived terms cannot ride on Rule 462(c) and must instead be made through an ordinary post-effective amendment subject to staff review and Commission action.

Regulatory framework

Three Securities Act rules govern the filing:

• Rule 430A permits the original omission of pricing information from the prospectus at effectiveness, allowing the registration statement to go effective before the deal is priced.
• Rule 462(c) makes a post-effective amendment whose only purpose is to add Rule 430A information effective immediately upon filing, with no acceleration, declaration, or waiting period.
• Rule 424(b)(1) governs the parallel obligation to file the final form of prospectus reflecting the pricing terms. POS462C is the registration-statement-level vehicle for the same pricing information that Rule 424(b) carries at the prospectus level.

POS462C is the EDGAR submission type code that signals invocation of the Rule 462(c) immediate-effectiveness procedure. The legal form of the document remains a post-effective amendment to the underlying registration form.

Timing and effectiveness

The defining timing feature is immediate effectiveness on filing under Rule 462(c). No staff review, no acceleration request, and no Commission order is involved.

The typical sequence is:

1. The registration statement is declared effective with a Rule 430A prospectus omitting pricing terms.
2. The offering is priced.
3. A final prospectus is filed under Rule 424(b)(1) within the prescribed window after pricing.
4. Where the registrant also amends the registration statement itself, a POS462C is filed and becomes effective on filing.

These records are event-driven and deal-specific, not periodic.

Earliest records

Rule 430A was adopted in 1987, and Rule 462 was later expanded to include the immediate-effectiveness procedure for pricing-completion post-effective amendments. POS462C submissions appeared on EDGAR as electronic filing was phased in for Securities Act registrants in the mid-1990s; the earliest records in this dataset are from June 1996.

How This Dataset Differs From Similar Datasets or Filings

Form POS462C occupies a narrow technical position: a post-effective amendment, immediately effective under Rule 462(c), that exists solely to add Rule 430A pricing information to an already-effective registration statement. Several nearby filings share part of that profile and are easy to confuse with it.

POS AM (general post-effective amendment)

POS AM is the umbrella post-effective amendment for substantive changes to an effective registration statement (material prospectus updates, new selling shareholders, restated financials). Two differences matter:

• Effectiveness: POS AM generally requires Commission action; POS462C is effective on filing.
• Scope: POS AM has no substantive scope limit; POS462C is restricted to previously omitted Rule 430A pricing terms.

Any update beyond pricing forces the registrant onto POS AM.

POS462B (Rule 462(b) post-effective amendment)

The closest sibling. Both forms are immediately effective post-effective amendments tied to Rules 462(b)/(c), but they answer different questions:

• POS462B registers up to 20 percent more securities of the same class at the same offering.
• POS462C registers no new securities; it only completes the registration with final Rule 430A pricing.

A single offering can produce both, for distinct purposes.

424B-series prospectuses (especially 424B1 and 424B4)

424B1 and 424B4 are the priced prospectuses filed after a Rule 430A omission. The overlap with POS462C is real — both reflect the same pricing event — but the layer is different:

• 424B-series filings update the prospectus delivered to investors; they do not amend the registration statement.
• POS462C amends the registration statement itself to fold pricing into the effective filing record.

Researchers reconstructing an IPO typically need both: 424B1/424B4 for the investor-facing prospectus and POS462C for the registration-statement record.

Underlying registration statements (S-1, F-1, and occasionally S-3/F-3)

POS462C is always an amendment to a previously effective base registration. Those base filings carry the substantive offering disclosure — risk factors, business, financials, use of proceeds. POS462C carries only the pricing completion. Linking POS462C to the base filing by registration-statement number is required to reconstruct the full offering. POS462C is overwhelmingly a Rule 430A artifact, so it is concentrated in non-shelf S-1 and F-1 offerings; shelf takedowns under Rule 430B are typically updated via 424(b)(2) or 424(b)(5) supplements rather than POS462C, which helps explain the small footprint of the corpus.

WKSI shelf takedowns and investment companies

WKSI shelf takedowns under Rule 430B generally do not use POS462C; Rule 430B has its own mechanics that route transaction-specific information through prospectus supplements. Investment companies and BDCs operate under separate Securities Act and Investment Company Act effectiveness regimes and typically do not produce POS462C filings.

Boundary summary

POS462C is defined by the intersection of three constraints: (1) post-effective amendment to a registration statement, (2) immediately effective on filing under Rule 462(c), and (3) limited to adding Rule 430A pricing with no other substantive change. Remove any one and a different form applies — POS AM for substantive amendments, POS462B for additional securities, 424B1/424B4 for the priced investor prospectus, and the base S-1/F-1 for the offering disclosure. The dataset is best used as a complement to those neighbors, providing the registration-statement-level record of final pricing for traditional non-shelf Rule 430A offerings.

Who Uses This Dataset

POS462C filings record the moment a registrant locks in final pricing for a registered offering under Rules 430A and 462(c). The dataset serves a focused set of professionals working on offering execution, disclosure mechanics, IPO research, and regulatory analytics.

Capital markets and securities attorneys

Counsel drafting post-effective pricing amendments use prior POS462C filings as a precedent bank. They focus on cover-page pricing tables, restated public offering price, underwriting discount language, and over-allotment terms to confirm the amendment stays within the 462(c) immediate-effectiveness pathway and contains no substantive changes beyond Rule 430A pricing information.

Disclosure counsel and registration specialists

These teams compare the amended registration statement number, exhibit lists, and pricing pages against the parent S-1 or F-1 to validate that updates fall within 462(c) rather than triggering a Rule 462(b) or full post-effective amendment.

ECM syndicate and execution teams

Bankers benchmark offering size, price to public, underwriting spread, net proceeds, greenshoe sizing, and selling-shareholder allocations on comparable transactions, particularly to study cases where issuers used 462(c) instead of a 424(b) prospectus supplement.

IPO and event-driven research analysts

Analysts treat the updated prospectus as the definitive pricing record for first-day-return calculations, allocation modeling, league tables, and aftermarket performance studies.

New-issue data vendors

Vendors ingest POS462C accessions to populate final offer price, deal size, registration linkage, issuer CIK, filing timestamp, and underwriter identity. Predictable EDGAR submission structure supports automated parsing pipelines.

RegTech and compliance automation teams

Engineers train classifiers that distinguish 462(b), 462(c), 462(d), and ordinary post-effective amendments, and extract pricing fields, registration cross-references, and effectiveness timestamps from the standardized form.

In-house compliance and corporate secretarial staff

Issuer-side teams use prior filings to plan their own pricing-night mechanics: which exhibits to re-file or incorporate by reference, signature-page structure, and pricing-supplement language.

Forensic accountants and litigation support

In Section 11 disputes, allocation claims, and selling-shareholder disclosure issues, the prospectus inside the POS462C is the operative offering document. The dataset provides authenticated archival copies with accession-level metadata.

Academic finance and securities-law researchers

The 1996-to-present corpus supports longitudinal work on underpricing, partial-adjustment behavior, the choice between 424(b) and 462(c) routes, and the textual evolution of pricing-amendment language.

Data engineers and RAG developers

Teams building offering-document pipelines and retrieval systems use POS462C documents so question-answering tools route pricing queries to the operative amendment rather than an earlier, pre-priced prospectus.

Surveillance and audit reconciliation teams

Exchange surveillance, SRO staff, and internal audit functions reconstruct the offering record around specific tickers, confirm timely filing, and flag missing or delayed amendments relative to trading activity using accession metadata, CIK, and timestamps.

Specific Use Cases

The Form POS462C corpus is small and procedurally narrow, which makes it useful for tightly scoped workflows that depend on the final-pricing snapshot of a registered offering.

Building an IPO final-pricing reference table

Parse the primary POS462C document for each accession to extract the offering box (public offering price, shares offered, underwriting discount, net proceeds, greenshoe size) and the recomputed Calculation of Registration Fee table. Joined to entities[].cik, entities[].fileNo, and effectivenessDate from metadata.json, the result is a deal-level table keyed to the underlying S-1 or F-1 that supports first-day return studies, league-table construction, and partial-adjustment analysis.

Linking pricing amendments to the parent registration statement

Use entities[].fileNo (the 333-... registration number) to join each POS462C record to its base S-1, F-1, S-3, or F-3 and to any 424B1 or 424B4 prospectus filed in the same offering. This lets researchers reconstruct the full document chain — base registration, priced prospectus, and registration-statement pricing amendment — and reconcile pricing terms across the three filings for a single deal.

Precedent bank for drafting Rule 462(c) amendments

Capital markets counsel can pull prior POS462C filings filtered by SIC, jurisdiction (stateOfIncorporation), or underwriter to retrieve cover pages, restated offering boxes, and exhibit slates (EX-5.1 legal opinion, EX-23.x consents) as drafting precedent. The standardized SGML envelope and documentFormatFiles[] manifest make it straightforward to assemble a precedent set scoped to comparable transactions.

Training a form-classifier for 462(b) vs 462(c) vs POS AM

The corpus provides clean POS462C exemplars for supervised classification tasks that distinguish immediately-effective pricing amendments from 462(b) over-allotment registrations, ordinary POS AM amendments, and 424B-series prospectus supplements. Features drawn from the cover page, fee table, and exhibit list — combined with formType and description from the manifest — support both rule-based extractors and language-model fine-tuning for filing-routing pipelines.

Authenticated prospectus retrieval for Section 11 and allocation disputes

For litigation involving the registered offering, the POS462C primary document is the operative pricing prospectus. The dataset supplies the SGML-wrapped HTML payload together with accession-level metadata (accessionNo, filedAt timestamp, linkToFilingDetails) so litigation support and forensic accounting teams can produce an authenticated archival copy and a verifiable filing chain of custody.

Routing pricing questions in offering-document RAG systems

Data engineers building question-answering systems over offering documents can index POS462C documents alongside the parent S-1 or F-1 and tag them with effectivenessDate and fileNo. Retrieval can then prefer the POS462C payload for queries about final price, proceeds, and underwriting spread, ensuring answers come from the operative amendment rather than an earlier pre-priced prospectus.

Dataset Access

Dataset Index JSON API: https://api.sec-api.io/datasets/form-pos462c-files.json This endpoint returns dataset metadata including name, description, last updated timestamp, earliest sample date, total records and total size, covered form types, container format, and content file types. It also lists every container file in the dataset with per-container size, record count, last updated timestamp, and a direct download URL. Use this index to monitor which containers were updated in the most recent refresh run and to decide which containers to download on a daily basis. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a14-8825-07f5892cccd2",
        

          3
            "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-pos462c-files.zip",
        

          4
            "name": "Form POS462C Files Dataset",
        

          5
            "updatedAt": "2026-04-16T08:25:09.313Z",
        

          6
            "earliestSampleDate": "1996-06-01",
        

          7
            "totalRecords": 246,
        

          8
            "totalSize": 9426676,
        

          9
            "formTypes": ["POS462C"],
        

          10
            "containerFormat": "ZIP",
        

          11
            "fileTypes": ["TXT", "JSON", "HTML"],
        

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-pos462c-files/2026/2026-03.zip",
        

          15
                "key": "2026/2026-03.zip",
        

          16
                "size": 124583,
        

          17
                "records": 3,
        

          18
                "updatedAt": "2026-04-16T08:25:09.313Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: https://api.sec-api.io/datasets/form-pos462c-files.zip?token=YOUR_API_KEY Downloads the full Form POS462C dataset as a single ZIP archive containing all monthly containers from June 1996 to the most recent refresh. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-pos462c-files/2026/2026-03.zip?token=YOUR_API_KEY Downloads one individual monthly container ZIP instead of the full dataset. Replace the year and month segments to target a specific period. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form POS462C, the EDGAR designation for a post-effective amendment to a Securities Act of 1933 registration statement that becomes effective immediately on filing under Rule 462(c). The amendment is used solely to add Rule 430A pricing information that was previously omitted from an already-effective prospectus.

What does one record in this dataset represent?

Each record is a single EDGAR accession of a Form POS462C filing, packaged as an accession folder named with the 18-digit unhyphenated accession number. The folder contains a metadata.json manifest plus the SGML-wrapped HTML primary document and any text-bearing exhibits (typically EX-5.1 legal opinions and EX-23.x consents).

Who is required to file Form POS462C?

The filer is the same Securities Act registrant that originally registered the securities under the underlying form (most commonly S-1, F-1, S-3, F-3, or S-11). No third party files this amendment. The filing is triggered when the registrant has determined the final pricing terms of an offering that was made effective with a Rule 430A prospectus omitting those terms.

What time period does the dataset cover?

The dataset includes all Form POS462C filings submitted to EDGAR from June 1996 to the most recent refresh. Records are grouped into monthly ZIP containers under the layout <YYYY-MM>/<accessionNoDigits>/<files>.

What file formats are in the dataset?

Each accession folder contains a JSON manifest (metadata.json) and SGML-wrapped HTML/HTM documents for the primary POS462C amendment and its exhibits. The dataset's file-type vocabulary is JSON, HTML, and TXT. Image attachments such as logos and embedded charts (GRAPHIC entries) are referenced in the manifest but not bundled into the ZIP, and POS462C filings carry no XBRL.

How does Form POS462C differ from Form 424B1 or 424B4?

Both filings reflect the same pricing event, but they operate at different layers. 424B1 and 424B4 are the priced final prospectuses delivered to investors and filed under Rule 424(b)(1). POS462C amends the registration statement itself to fold the Rule 430A pricing into the effective filing record. Researchers reconstructing an IPO typically need both.

How can I link a POS462C record back to the original registration statement?

Use the entities[].fileNo field in metadata.json, which carries the 333-... registration file number. That number is the natural foreign key joining a POS462C record to the underlying S-1, F-1, S-3, or F-3 base filing and to any 424B-series prospectus supplements in the same offering.