Form AW WD Files Dataset

The Form AW WD Files Dataset is the complete EDGAR collection of AW WD submissions — the second-order procedural filings that Securities Act of 1933 registrants use to rescind a previously filed Form AW and thereby reinstate an amendment to a registration statement. Each record corresponds to exactly one accession-numbered EDGAR submission of form type AW WD and bundles the structured filing metadata together with the filer-submitted document(s), with image attachments excluded. The underlying Form AW is the registrant's request under Rule 477 of Regulation C (17 CFR 230.477) to withdraw a pre-effective or post-effective amendment to a registration statement; the AW WD rescinds that request before the staff acts, leaving the original amendment in force. Coverage begins in April 2002 — the period from which AW WD activity is indexed in EDGAR — and continues to the present. The dataset is distributed as monthly ZIP containers and contains HTML, JSON, TXT, and PDF files.

Dataset APIs

Dataset Files

What This Dataset Contains

A single record in the Form AW WD Files dataset corresponds to one accession-numbered submission of EDGAR form type AW WD. Each record bundles the structured filing metadata together with the filer-submitted document(s) that constituted the original EDGAR transmission, with image attachments excluded. The unit of observation is exactly one accession number; records are never aggregated across filers, registration statements, or months. The dataset as a whole is the union of every AW WD accession indexed on EDGAR from April 2002 through the present.

AW WD is a narrow administrative submission type whose sole purpose is to withdraw a previously filed Form AW. A Form AW is itself the registrant's request to withdraw a pre-effective or post-effective amendment to a registration statement filed under the Securities Act of 1933. The AW WD therefore operates two layers above the underlying registration statement: it rescinds a pending withdrawal request, leaving the originally filed amendment in place. Because the action is purely procedural and introduces no new substantive disclosure, the filing is effectively a short letter to the Commission identifying (a) the prior AW to be rescinded and (b) the registration statement and amendment to which the original AW referred. There is no prescribed form face, no Item-numbered structure, no financial statements, and no exhibit schedule — the substantive content of the filing reduces to the registrant's identification of the prior accession and its request to undo it.

Content Structure of a Single Record

Container and folder layout

The dataset is distributed as monthly ZIP containers keyed by calendar year and filing month, with the path convention YYYY/YYYY-MM.zip. Each ZIP, when extracted, produces a top-level directory named YYYY-MM/ that holds one subdirectory per accession contained in that month. Months with no AW WD filings are absent from the index rather than represented as empty containers; this is common because filings of this type are rare and individual months often carry only one to a few records.

Each accession folder is named after the SEC accession number with the dashes removed. An accession recorded in EDGAR as 0001213900-25-025677 becomes the directory 000121390025025677/. The canonical dashed form remains available inside metadata.json, so the folder name is a deterministic, dash-stripped projection of the underlying identifier (the conventional 10-2-6 split is reinserted when mapping back).

Inside one accession folder the contents are:

• metadata.json — always present, exactly one per record, holding the structured filing record.
• One or more filer-submitted document files. The file-types found in the dataset are HTM/HTML, TXT, and PDF (with JSON used only for the metadata sidecar). In modern filings the primary document is almost always a single HTM file, named exactly as it was submitted to EDGAR (for example ea023515801-awwd_valueadd.htm).

Image files referenced by submissions (signature scans, logos, other binary graphics) are excluded from the dataset by design. EDGAR's complete-submission .txt SGML envelope is referenced inside metadata.json but is not consistently packaged inside the ZIP; when present it appears as an additional file in the accession folder, and when absent it can be retrieved from the URL in linkToTxt.

metadata.json anatomy

metadata.json is a single JSON object holding one filing's structured record. Its fields fall into four logical groupings.

Filing identification:

• formType — fixed string "AW WD" for every record in this dataset.
• accessionNo — the SEC accession number in canonical dashed form, e.g. "0001213900-25-025677".
• filedAt — ISO 8601 timestamp with timezone offset capturing when EDGAR accepted the submission.
• description — short human-readable explanation of the form's purpose.
• id — opaque 32-character hexadecimal internal record identifier.

Source links to EDGAR:

• linkToFilingDetails — URL to the primary document on sec.gov/Archives.
• linkToTxt — URL to the complete-submission text file (the SGML envelope on EDGAR).
• linkToHtml — URL to the EDGAR filing index page.
• linkToXbrl — empty string for this form type.

Document inventory (documentFormatFiles) — array of document descriptors, one entry per file EDGAR recorded in the submission. Each entry contains:

• sequence — ordinal of the document within the submission, encoded as a string; the index/complete-submission entry may carry a single space.
• size — byte size of the file as a string.
• documentUrl — direct download URL on sec.gov.
• description — EDGAR-supplied description; for AW WD this is typically "REQUEST FOR WITHDRAWAL OF FORM AW", with minor variation in capitalization and wording across filers.
• type — EDGAR document type ("AW WD" for the primary letter, blank or space for the complete-submission text file).

Filer/subject entities (entities) — array of entity objects describing the parties associated with the submission. Each entry includes:

• companyName — entity name with role suffix in parentheses, e.g. "... (Filer)".
• cik — Central Index Key.
• type — relationship/form type for the entity, "AW WD" here.
• fileNo — Securities Act file number, e.g. "024-12588".
• filmNo — EDGAR film number assigned at acceptance.
• irsNo — IRS Employer Identification Number.
• act — Securities Act code under which the registration was filed.
• sic — Standard Industrial Classification code with description.
• stateOfIncorporation — two-letter state or country code.
• fiscalYearEnd — MMDD format.

Two array fields, seriesAndClassesContractsInformation and dataFiles, are present for consistency with broader EDGAR metadata conventions but are typically empty for this form type, since AW WD filings carry no series/class disclosures and no supplementary data files.

Document file anatomy

The filer-submitted document is wrapped in EDGAR's SGML document envelope, even when the inner payload is HTML. The envelope tags carry the classification fields used by EDGAR routing and indexing:

          1
          <DOCUMENT>
        

          2
          <TYPE>AW WD
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>ea023515801-awwd_valueadd.htm
        

          5
          <DESCRIPTION>REQUEST FOR WITHDRAWAL OF FORM AW
        

          6
          <TEXT>
        

          7
          <HTML>
        

          8
            ... letter body ...
        

          9
          </HTML>
        

          10
          </TEXT>
        

          11
          </DOCUMENT>
        

Inside <TEXT>, modern filings contain an <HTML> document with a minimal <HEAD> and a <BODY> styled in a serif typeface that mimics standard correspondence formatting. The narrative body is short and follows a recognizable letter pattern, generally in the following order:

1. Registrant letterhead or name block.
2. Date and addressee block, typically directed to the U.S. Securities and Exchange Commission, Division of Corporation Finance.
3. A RE: line citing the Securities Act file number and the registration or offering statement at issue.
4. One or two body paragraphs identifying the prior Form AW (commonly by accession number and filing date) and requesting that the previously submitted withdrawal request itself be withdrawn so that the underlying amendment remains in effect.
5. A short statement of the reason for rescinding the prior withdrawal — e.g. a clerical correction, a change of strategy on the registration, or recognition that a different form should have been used (such as Form 1-A-W for Regulation A offerings).
6. A signature block from a registrant officer or counsel, including name, title, and contact information.

There is no standardized cover page, no Item-numbered structure, and no financial or tabular content. PDF documents appear in some records when the filer submitted a scanned or rendered letter rather than HTML; TXT documents typically correspond to the EDGAR complete-submission envelope when bundled.

What is included in a record

Each record contains the full structured metadata for the filing and every filer-submitted document EDGAR retained, with the exception of image attachments. In practice this means the primary AW WD letter as HTM (or PDF) and any additional textual documents EDGAR recorded for the submission. metadata.json also preserves the canonical EDGAR URLs, so the original submission — including any artifacts excluded from the local copy — can always be reconstructed from sec.gov.

What is excluded or structurally separate

Image files referenced by the submission (signature scans, registrant logos, other binary graphics) are deliberately omitted. The EDGAR complete-submission .txt SGML envelope is described inside documentFormatFiles but is not consistently packaged inside the ZIP; when it is absent locally, linkToTxt provides the canonical retrieval path. The EDGAR filing-index HTML page is not bundled inside the accession folder; it is referenced through linkToHtml. Filings of related but distinct types — the underlying AW request, the original registration statement, or its amendments — are separate accessions and are not part of any record in this dataset; their identifiers commonly appear inside the AW WD letter body but the documents themselves live in their own filings.

Structural and historical notes

Coverage begins in April 2002, the period from which AW WD activity is indexed in EDGAR, and continues to the present. Because the form is procedural and rare, the underlying filing's structure has not changed materially over time: the submission has always been a short identifying letter rather than a structured form. The variation visible across the dataset is therefore in document format rather than form content — earlier filings are more likely to consist of plain-text or scanned PDF letters, while later filings are predominantly HTM documents wrapped in the SGML envelope.

Across all years, the per-record anatomy is uniform: one metadata.json, one primary document (occasionally accompanied by a complete-submission text file), the same SGML wrapper around the document body, and the same accession-folder naming convention. This consistency makes the dataset straightforward to traverse programmatically: enumerate monthly ZIPs, extract each YYYY-MM/ directory, iterate accession subfolders, parse metadata.json for structured identifiers, and read the referenced document file from the same folder.

Interpretation and extraction notes

A few nuances matter for downstream use.

• Identifier mapping. The accession folder name is dash-stripped while metadata.json.accessionNo is dash-formatted; mapping between the two requires inserting or removing dashes at the conventional 10-2-6 split.
• Local vs. canonical paths. The documentFormatFiles[*].documentUrl values point to sec.gov and are not paths inside the ZIP; to locate the local copy, take the basename of documentUrl and look for it in the accession folder.
• Description variability. The description field on documentFormatFiles is filer- or EDGAR-supplied free text; "REQUEST FOR WITHDRAWAL OF FORM AW" is the dominant phrasing but capitalization and exact wording vary.
• Embedded cross-references. Inside the letter body, the prior AW accession is typically present in plain text and can be extracted with simple regex over the rendered HTML, but the exact position and labeling vary by filer; the registration file number on the RE: line is a more stable anchor.
• Document-to-entity linkage. The entities array commonly contains a single filer with a (Filer) role suffix, but a single submission may list multiple entities when several registrants are jointly identified on the underlying registration statement.
• Indexing feasibility. Because the dataset is small and each filing is short, full-text indexing of every document is feasible without significant storage overhead, and end-to-end parsing of metadata plus letter body is inexpensive per record.

Who Files or Publishes This Dataset, and When

Who files

Each record is a single EDGAR submission of type AW WD made by a Securities Act of 1933 registrant — the same legal entity (same CIK) that previously filed both an amendment to a registration statement and a Form AW seeking to withdraw that amendment under Rule 477. The submission is signed by an authorized officer of the registrant (CEO, CFO, general counsel, or secretary) or by outside counsel acting under a power of attorney already on file with the registration statement.

The filer population is a strict subset of Form AW filers, which is itself a subset of Securities Act registrants:

• Securities Act registrants. Domestic and foreign issuers with a pending or effective registration statement on Form S-1, Form S-3, Form S-4, Form S-8, Form S-11, Form F-1, Form F-3, Form F-4, or comparable forms, including pre-effective amendments and post-effective amendments. Corporate issuers, business trusts, limited partnerships, REITs, and foreign private issuers all qualify.
• Registrants that already filed a Form AW. Form AW WD only exists in relation to a prior Form AW on the same registration file.
• Regulation A note. A small number of records correspond to Regulation A offering statements (Form 1-A) where the filer indicates Form 1-A-W would have been the proper vehicle; the AW WD here rescinds an AW that was filed in error.

The filing is rare because it is only relevant in the unusual case where a registrant files a Form AW and then reverses that decision before the staff acts.

When the record is created

Form AW WD is event-driven, not periodic, and has no statutory deadline. The trigger sequence is:

1. The registrant has on file an amendment to a Securities Act registration statement.
2. The registrant has filed a Form AW under Rule 477 of Regulation C (17 CFR 230.477) requesting withdrawal of that amendment.
3. The registrant decides — typically due to changed offering plans, a corrected filing strategy, or recognition that a different form should have been used — that it wants the amendment to remain on file.
4. The registrant submits Form AW WD to EDGAR to rescind the prior Form AW.

The practical filing window is bounded on the front end by the date of the related Form AW and on the back end by the date the staff acts on that Form AW. Once the underlying amendment has been formally withdrawn, there is nothing left for an AW WD to operate on, so AW WD filings typically appear within days or a few weeks of the corresponding AW. EDGAR timestamps the filing on receipt; there is no acceptance or effectiveness step.

Regulatory framework

Rule 477 of Regulation C (17 CFR 230.477) governs withdrawal of registration statements and amendments under the Securities Act of 1933. It provides that an application to withdraw is deemed granted unless the Commission objects within 15 days. Form AW is the EDGAR submission type used to make that application with respect to an amendment; Form RW is the parallel submission used to withdraw an entire registration statement. Form AW WD is the EDGAR submission type used to rescind a previously filed Form AW before the Rule 477 process completes.

Form AW WD is procedural only. It does not register securities, amend disclosure, or replace exhibits. Its sole function is to operate on the procedural record of a previously filed Form AW.

Important distinctions

• Form AW vs. Form AW WD. Form AW withdraws an amendment; Form AW WD withdraws the Form AW. They are paired but distinct EDGAR submission types.
• Form RW vs. Form AW. Form RW withdraws an entire registration statement under Rule 477; Form AW operates only at the amendment level. The corresponding rescission of a Form RW is filed as RW WD, a separate dataset.
• Form 1-A-W (Regulation A). Withdrawal of a Regulation A offering statement uses Form 1-A-W rather than Form AW; AW WD is occasionally used to undo an AW filed in error against a Reg A offering.
• Filer equals subject. The reporting party and the affected registrant are the same legal entity, unlike beneficial-ownership filings where filer and issuer differ.
• No staff approval. Form AW WD is the registrant's unilateral submission, not a Commission order. It moots the pending AW request rather than seeking affirmative consent.
• Coverage start. The dataset begins April 2002, reflecting when AW WD became an indexed EDGAR submission type. Equivalent rescission requests before that date were handled as paper correspondence with the Commission.

How This Dataset Differs From Similar Datasets or Filings

Form AW WD is a second-order procedural filing: it rescinds a prior request to withdraw an amendment to a Securities Act registration statement. The most useful comparisons are to the action it reverses (Form AW), to the parallel pair operating one level up at the full registration-statement level (Form RW and Form RW WD), and to the substantive registration and prospectus filings whose lifecycle these procedural forms touch.

Form AW — the action being rescinded

Form AW is filed under Rule 477 to obtain the Commission's consent to withdraw a specific pre-effective or post-effective amendment. Form AW WD is filed only when the registrant later wants that AW request itself pulled back, leaving the underlying amendment in force. AW is the upstream event; AW WD is the reversal. AW is meaningfully more common because most withdrawal requests are not themselves rescinded. Any AW WD filing is fully interpretable only when joined to the prior AW it cancels, typically by registration-statement number or accession reference in the cover letter.

Form RW — same intent, one level up

Form RW requests withdrawal of an entire registration statement, not a single amendment. The object of the action is the difference: RW removes the whole filing from the registration track; AW removes a single amendment within it. Form AW WD never operates on RW filings. Researchers tracking abandoned offerings use RW; researchers tracking reversed amendment-level withdrawals use AW WD.

Form RW WD — the structural twin

Form RW WD is the closest sibling to Form AW WD: same procedural shape, same rarity, same letter-plus-metadata content. The only substantive difference is what gets reinstated — a full registration statement (RW WD) versus a single amendment (AW WD). A complete view of reinstated offering activity requires both datasets; neither substitutes for the other.

Pre-effective vs. post-effective amendments

Both kinds of reinstated amendments file under the same AW WD form type; the dataset does not split them. The distinction matters analytically — reinstating a pre-effective amendment affects the path to effectiveness, while reinstating a post-effective amendment updates an already-live offering — but it must be recovered from the cover letter or the registration-statement context, not the form code.

Registration-statement amendment forms (S-1/A, S-3/A, F-1/A, S-4/A, etc.)

These are the substantive documents whose status Form AW WD restores. An S-1/A or F-1/A carries the updated prospectus, financial statements, risk factors, and offering terms; AW WD carries none of this. AW WD is a short procedural notice that points at one of these amendments by accession or registration number. To know what is actually being reinstated, the AW WD record must be joined to the referenced amendment.

Rule 424 prospectus filings (424B1–B5, 424A, etc.)

Rule 424 filings are the operative prospectus delivered to investors after effectiveness — pricing, terms, supplements. AW WD has no prospectus content, no offering economics, and no investor-facing disclosure. The two datasets sit on different layers: 424 documents the live offering; AW WD documents a procedural reversal affecting whether a particular amendment remains on the record. Neither dataset reveals anything about the other's domain.

Boundary summary

Form AW WD is the only EDGAR submission type that rescinds an Application for Withdrawal of a registration-statement amendment. It is procedural, very low volume, and meaningful only against the AW filing it reverses and the amendment whose status it restores. Form AW is its required upstream context, Form RW WD is its structural twin one level up, and the S-3/A-family (S-4/A included) amendments together with 424B1/424B5/424A prospectus filings are the substantive documents these procedural forms act on. No other dataset substitutes for AW WD when the question is specifically about reversed amendment-withdrawal requests, but several must be joined to it to make each event interpretable.

Who Uses This Dataset

This is a narrow corpus: every existing instance of a rare procedural form type, in original textual form. The users are specialists who need precedent, procedural reconstruction, or completeness work. It is not a dataset for fundamental analysts, credit teams, or quant signal builders.

Securities lawyers drafting an AW WD letter

Outside counsel and in-house securities lawyers preparing one of these letters use the dataset as a precedent library. Without examples, drafting means inventing language from scratch. They pull the letter exhibits to study how prior filers phrased the rescission, cited the original Form AW, identified the underlying registration statement and amendment number, and stated their rationale to staff. The metadata supplies filer CIK, accession number, and filing date; the document body supplies the language counsel adapts. Output: a submission the staff accepts without follow-up.

Capital markets attorneys reconstructing registration-statement histories

Attorneys advising on shelf takedowns, follow-ons, or further amendments need to know what is currently live before the Commission when a registrant's file shows a Form AW followed by an AW WD. They read the rescission letter directly rather than infer status from headers, focusing on the registration file number, the amendment identifier in the letter, and the explicit rescission language. The output is a defensible procedural timeline used in legal opinions, comfort letters, and offering process memos.

Regulatory researchers and policy analysts

Analysts studying low-frequency procedural mechanisms can review the full population. They use cover letter narratives, the time gap between the underlying AW and the AW WD, and the categories of filers involved to assess how often rescissions occur, what triggers them, and how the practice has shifted since 2002. The work feeds internal policy reviews, staff guidance updates, and historical context for rule-making.

Academic researchers studying registration-statement lifecycles

Securities-regulation and corporate finance researchers treat the AW WD population as a complete-universe sample of an unusual procedural reversal. They join it to S-1, S-3, S-4, their amendments, and the corresponding AW filings to build event histories. Key fields: filing date, registrant identifier, registration statement number cited inside the letter, and the underlying AW accession being rescinded. Outputs are descriptive statistics and event-study controls for withdrawn-then-reinstated amendments.

EDGAR data engineering teams ensuring form-type completeness

Teams mirroring EDGAR for downstream products cannot leave gaps without breaking lineage and reconciliation checks. Even at trivial volume, an absent form type creates ambiguity. Engineers ingest the corpus to confirm completeness, validate parsers against the actual document structures (HTML, TXT, PDF), and verify that accession indexes and filer-history tables include every legitimate submission. Metadata is the primary input; payloads validate text-extraction on a long-tail form.

Filing-history analysts at law firms and corporate secretarial groups

Analysts maintaining issuer filing chronologies need to know which amendments are operative, which are withdrawn, and which withdrawals have been rescinded. This is the only authoritative source for the rescission step in machine-readable form. They use the registrant identifier, registration file number, and cross-references to the original AW accession to update diligence binders and procedural status memos for transactional teams.

Litigation-support and forensic researchers

In disputes touching the timing or status of a securities offering, the precise date and content of an AW WD letter can be material. These users capture the filing timestamp from metadata, read the cover letter, and preserve the original document as an exhibit-quality artifact for expert reports and fact chronologies.

RAG and retrieval-system developers building exhaustive SEC corpora

Teams building question-answering systems over the full EDGAR population include this corpus so questions about obscure procedural forms return grounded, citation-backed answers. Text payloads feed embedding indexes; metadata supplies filter facets (form type, CIK, filing date). Marginal storage cost is negligible; marginal completeness benefit is meaningful for narrow procedural queries.

Specific Use Cases

Building a precedent library for AW WD letter drafting

Securities counsel preparing an AW WD submission pull every prior letter to study how filers cited the original Form AW accession, identified the registration statement and amendment number on the RE: line, phrased the rescission request, and explained the rationale to staff. The HTM/PDF letter bodies supply adaptable language; metadata.json supplies filer CIK, file number, and filing date for context. Output is a draft letter modeled on accepted submissions.

Reconstructing registration-statement procedural histories

Capital markets attorneys advising on shelf takedowns or follow-ons need to confirm what is currently live before the Commission when an issuer's filing chronology shows AW followed by AW WD. They extract the registration file number and prior AW accession from the letter body, join to the underlying S-1/A, S-3/A, or F-1/A, and produce a defensible amendment-status timeline used in legal opinions, comfort letters, and process memos.

Empirical research on Rule 477 withdrawal practice

Regulatory researchers and academics treat the corpus as a complete-universe sample of reversed Rule 477 withdrawal requests. Useful variables include filedAt, the time gap to the referenced AW, the SIC and state-of-incorporation fields in entities, and the filer-stated reason text in the letter body. Outputs are descriptive statistics on rescission frequency, triggering circumstances (clerical error, change of strategy, wrong-form selection), and shifts in practice since 2002.

Complete-corpus engineering and EDGAR mirror reconciliation

Teams mirroring EDGAR ingest the full corpus to close a long-tail form-type gap that would otherwise break lineage checks against the EDGAR full-index. Engineers validate accession-folder naming (dash-stripped vs. dashed accessionNo), confirm parser behavior across the HTM, TXT, and PDF document variants, and verify that filer-history tables surface every AW WD against the issuer's CIK. The full corpus fits comfortably in a single small index.

Exhaustive RAG and retrieval datasets for procedural EDGAR questions

Developers building question-answering systems over the full EDGAR population embed every AW WD letter so that queries about obscure procedural reversals return citation-backed answers rather than hallucinations. Letter text feeds the embedding index; formType, cik, filedAt, and fileNo from metadata.json provide filter facets. Storage cost is negligible; the completeness payoff is concentrated on narrow procedural questions where omission would otherwise produce a confident wrong answer.

Litigation and forensic timeline reconstruction

In disputes where the precise status of an offering amendment is material, litigation-support teams use the dataset as an exhibit-quality source for the rescission step. The filedAt timestamp anchors the event in a chronology, the letter body documents intent and the specific AW being undone, and linkToFilingDetails plus linkToTxt preserve canonical EDGAR provenance for expert reports and fact-witness chronologies.

Dataset Access

Dataset Index JSON API: https://api.sec-api.io/datasets/form-aw-wd-files.json

This endpoint returns the dataset metadata and the list of all container files available for download. Returned fields include the dataset name, description, last update timestamp, earliest sample date (2002-04-01), total record count, total dataset size, form types covered (AW WD), container format (ZIP), and file types contained inside each container (HTML, JSON, TXT, PDF). Each container entry includes its object key, size, record count, last updated timestamp, and direct download URL. This endpoint does not require an API key and can be polled to detect which containers were updated in the most recent refresh, so downstream pipelines can re-download only the changed containers. Given the small total dataset size, most users will simply re-download the full archive on each refresh rather than tracking individual containers.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a05-9891-8edd6eac3a33",
        

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

          4
            "name": "Form AW WD Files Dataset",
        

          5
            "updatedAt": "2026-04-15T18:21:57.398Z",
        

          6
            "earliestSampleDate": "2002-04-01",
        

          7
            "totalRecords": 124,
        

          8
            "totalSize": 386211,
        

          9
            "formTypes": ["AW WD"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818,
        

          17
                "records": 2,
        

          18
                "updatedAt": "2026-04-15T18:21:57.398Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: https://api.sec-api.io/datasets/form-aw-wd-files.zip?token=YOUR_API_KEY

Downloads the entire dataset as a single ZIP archive containing all monthly containers from 2002 to the most recent refresh. Because the dataset is small, downloading the full archive in one request is practical for any workflow. This endpoint requires a valid sec-api.io API key passed via the token query parameter.

Download Single Container: https://api.sec-api.io/datasets/form-aw-wd-files/2026/2026-03.zip?token=YOUR_API_KEY

Downloads one individual monthly container instead of the full archive. Container paths follow the YYYY/YYYY-MM.zip pattern returned in the key field of each container entry from the index API. This endpoint requires a valid sec-api.io API key.

Frequently Asked Questions

What does Form AW WD do?

Form AW WD rescinds a previously filed Form AW. Because Form AW is the registrant's request under Rule 477 to withdraw an amendment to a Securities Act registration statement, filing a Form AW WD before the staff acts leaves that amendment in force on the registration file.

What does one record in this dataset represent?

Each record corresponds to exactly one accession-numbered EDGAR submission of form type AW WD. A record bundles the structured filing metadata (metadata.json) together with every filer-submitted document EDGAR retained for that submission, except image attachments.

Who is required to file Form AW WD?

Only Securities Act of 1933 registrants that previously filed both an amendment to a registration statement and a Form AW seeking to withdraw that amendment can file an AW WD. The submission is signed by an authorized officer of the registrant or by outside counsel acting under a power of attorney already on file.

How is Form AW WD different from Form AW and Form RW WD?

Form AW withdraws an amendment to a registration statement; Form AW WD withdraws that Form AW. Form RW WD is the structural twin one level up — it rescinds a Form RW that sought to withdraw an entire registration statement. AW WD operates only at the amendment level and never against an RW filing.

What time period does the dataset cover?

Coverage begins in April 2002 — the period from which AW WD activity is indexed in EDGAR — and continues to the present. Equivalent rescission requests before that date were handled as paper correspondence with the Commission and are not part of this dataset.

What file format is the dataset distributed in?

The dataset is distributed as monthly ZIP containers keyed by calendar year and filing month, with the path convention YYYY/YYYY-MM.zip. Inside each accession folder, files are HTML/HTM, JSON (used for the metadata.json sidecar), TXT, or PDF; image files are deliberately excluded.

How often are new records added?

Form AW WD is event-driven, not periodic, and has no statutory deadline. New records appear only when a registrant that has filed a Form AW decides to rescind that withdrawal request before the staff acts, which is rare; many months contain no AW WD filings at all and are absent from the index rather than present as empty containers.