Form RW WD Files Dataset

The Form RW WD Files Dataset packages every EDGAR submission of form type RW WD — the Withdrawal of a Registration Withdrawal Request — filed under Rule 477 of the Securities Act of 1933. Each record is one complete RW WD submission, identified by its SEC accession number and consisting of a metadata.json header plus the registrant's submitted documents (the brief, letter-style communication that reverses a prior Form RW, together with any cover correspondence). The form is filed by the issuer/registrant — domestic operating companies, foreign private issuers, investment companies, BDCs, and asset-backed issuers — whose Securities Act registration statement was the subject of an earlier Rule 477 withdrawal request. Coverage runs from May 2002 to the present, and records are distributed in monthly ZIP containers containing TXT, JSON, HTML, and PDF files.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset is built from EDGAR's RW WD submission type, a procedural housekeeping filing that reverses a previously filed Form RW and leaves the original Securities Act registration statement on file as if the withdrawal had never been requested. A Form RW (Rule 477) is itself a request that the Commission consent to the withdrawal of a not-yet-effective registration statement (such as an S-1, S-3, S-3ASR, S-4, F-1, or F-3); a Form RW WD undoes that withdrawal request. Because the form's only role is to communicate that the registrant no longer wishes its earlier withdrawal request to stand, the underlying document is a brief, letter-style communication addressed to the SEC's Division of Corporation Finance rather than a structured form with prescribed line items.

The dataset spans the full EDGAR population of RW WD filings from May 2002 through the present and is distributed as monthly ZIP containers. File types found inside a record include TXT, JSON, HTML, and PDF. Because Form RW WD is a low-volume submission type, monthly archives are typically small, often containing only one or two filings.

Content Structure of a Single Record

What one record represents

A single record in the Form RW WD Files dataset is one complete EDGAR submission of form type RW WD, uniquely identified by its SEC accession number. On disk a record is a folder named after the digits-only accession number (for example 000071507225000033) that bundles a metadata.json describing the submission together with every document the registrant attached, with the sole exception of image files.

Container and record packaging

Records are distributed in monthly ZIP containers. Each ZIP expands to a top-level folder named after the year-month (for example 2025-02/), under which one subfolder exists per accession number. The accession-number folder is the record. Inside that folder are exactly two kinds of files:

• a metadata.json describing the submission, the filer, and the document inventory; and
• the original EDGAR submission documents — the withdrawal-reversal letter itself plus, where present, any cover correspondence or supporting attachments.

The metadata.json is universally present; the document files vary in count and type from filing to filing.

Structure of metadata.json

The metadata file is a single JSON object that mirrors the EDGAR submission header and document index. The principal fields are:

• formType — always "RW WD" for records in this dataset.
• accessionNo — the SEC accession number rendered with dashes (for example "0000715072-25-000033").
• filedAt — an ISO 8601 timestamp with timezone offset reflecting when EDGAR accepted the filing.
• description — a human-readable label, typically "Form RW WD - Withdrawal of Registration Withdrawal Request".
• linkToFilingDetails, linkToTxt, linkToHtml, linkToXbrl — canonical URLs on sec.gov pointing respectively to the primary submission document, the complete-submission SGML/text wrapper, the EDGAR filing index page, and any XBRL data. The linkToXbrl field is empty for this form type because RW WD filings do not carry XBRL.
• id — a stable hash identifier for the record.
• documentFormatFiles — an array of objects, one per attached document, each carrying sequence, size (bytes, as a string), documentUrl, description, and type. The complete-submission .txt SGML wrapper is included as one entry (with blank type and sequence), alongside the registrant's actual letter and any supplementary documents.
• entities — an array of party objects describing the filer and any co-filers. Each entity object includes:
  • cik — SEC Central Index Key.
  • companyName — legal name with role suffix, for example "RENASANT CORP (Filer)".
  • type — the form type for that entity ("RW WD").
  • fileNo — the SEC file number of the registration statement being addressed (for example "333-284786"); this is the cross-reference that ties the RW WD back to the original Securities Act registration.
  • filmNo — EDGAR film number assigned to the filing.
  • irsNo — IRS employer identification number.
  • sic — Standard Industrial Classification code and description (for example "6022 State Commercial Banks").
  • stateOfIncorporation — two-letter state or country code.
  • fiscalYearEnd — MMDD format.
  • act — the securities act under which the filing was made (the 1933 Act).
  • tickers — an array of ticker symbols where applicable.
• seriesAndClassesContractsInformation — an array of investment-company series and class/contract identifiers, populated only when an investment company is the registrant; empty for typical operating-company filings.
• dataFiles — an array of structured data files; consistently empty for Form RW WD because this submission type does not carry XBRL or other structured exhibits.

For analytical use, the most important header-level field is entities, which carries both the registrant identity (CIK, name, SIC, state, ticker) and, in fileNo, the explicit linkage to the registration statement whose prior withdrawal is being reversed.

Structure of the filer's documents

Beyond metadata.json, the record carries the actual submission body. The file-types found in the dataset are TXT, JSON, HTML, and PDF; in practice, modern records are dominated by HTM/HTML letters plus the JSON manifest, with occasional PDF correspondence and the SGML/TXT complete-submission wrapper that EDGAR generates around any submission. Each non-metadata document is wrapped in the EDGAR SGML <DOCUMENT> envelope and carries its payload inside <TEXT>, following the canonical pattern:

          1
          <DOCUMENT>
        

          2
          <TYPE>RW WD
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>formrw2102025.htm
        

          5
          <DESCRIPTION>RW WD
        

          6
          <TEXT>
        

          7
          <html> ... letter body ... </html>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

The <TYPE> tag asserts the document role (RW WD for the primary letter, CORRESP for cover correspondence, GRAPHIC for excluded image attachments), <SEQUENCE> orders the documents within the submission, <FILENAME> matches the file as it appears in the accession folder, and <DESCRIPTION> is a short free-text label.

Typical contents of the withdrawal-reversal letter

The substantive payload is a short letter, typically on the registrant's or outside counsel's letterhead, addressed to the U.S. Securities and Exchange Commission, Division of Corporation Finance. Although the document is unstructured prose rather than a fielded form, a stable set of elements recurs:

• a date line and salutation;
• a citation to Rule 477 under the Securities Act of 1933, the regulatory basis for both the original Form RW and its reversal;
• identification of the affected registration statement by form (S-1, S-3, S-3ASR, S-4, F-1, F-3, etc.) and by Commission file number (for example 333-284786), often including the original filing date;
• reference to the prior Form RW submission, typically by the date the withdrawal request was filed and sometimes by accession number;
• an affirmative representation that no securities have been sold under the registration statement and, for not-yet-effective registrations, that the registration statement was never declared effective;
• a substantive explanation of why the registrant is reversing the withdrawal — recurring reasons include an administrative or tagging error in the original RW (for example a Form S-3 filed under the wrong tag and intended to be S-3ASR), a change in the registrant's strategic plans that makes continuing the registration desirable again, or correction of an inadvertent withdrawal;
• a request that the Commission treat the prior Form RW as withdrawn and reinstate the original registration statement;
• closing courtesies and a signature block identifying the signatory by name and title (commonly general counsel, corporate secretary, or outside securities counsel acting on behalf of the registrant).

Where outside counsel signs, the firm's letterhead and contact information replace the registrant's. Where the filing involves multiple registrants or guarantors (typical for shelf registrations with subsidiary co-registrants), the letter may identify each affected file number.

Included content

The record includes:

• the metadata.json header, document index, and entity block described above;
• the complete-submission SGML/TXT wrapper that EDGAR generates around the submission;
• the primary RW WD letter document, in HTML, plain text, or PDF as filed;
• any cover correspondence (CORRESP-typed documents) or supporting attachments other than images.

Excluded content

Image files attached to the original EDGAR submission — typically logo graphics or scanned signature blocks tagged as GRAPHIC documents — are deliberately excluded from the dataset packaging. Their absence does not affect the textual or legal content of the letter; it removes only embedded raster artwork. Material referenced by the letter but not attached to the submission (the underlying registration statement on Form S-/F-, the prior Form RW filing, or related correspondence filed under separate accession numbers) is also outside the record and must be retrieved via the file number or by following the EDGAR filing history of the registrant.

Stability of content over time

Form RW WD is a narrowly defined procedural submission with no enumerated Items, no required schedules, and no prescribed financial disclosures. Its content has therefore been stable across the May 2002 to present span of the dataset. The Rule 477 framework that governs Form RW (and by symmetry the reversal of an RW) has not been substantively re-engineered during this period, so the canonical letter — identification of the registration statement by file number, reference to the prior withdrawal, and a stated reason for reversal — looks essentially the same in the earliest records and the most recent. The only meaningful evolution is at the margins: more recent letters are more likely to cite Rule 477 explicitly, to recite the "no securities sold and not declared effective" representation in standardized language, and to reference subsequent corrective filings (for example noting that an S-3 will be refiled as S-3ASR).

Stability of data format over time

The presentation format of the underlying letter has shifted with EDGAR's broader format conventions. Filings from the early 2000s frequently appear as plain ASCII or simple TXT documents wrapped in the SGML <DOCUMENT>/<TEXT> envelope; HTML letters became progressively more common through the 2000s and 2010s and now dominate the population, with PDF appearing occasionally as cover correspondence or as a scan of a signed letter. The SGML complete-submission wrapper (linkToTxt) is consistent across the entire history of the dataset, as is the metadata.json structure, which is imposed uniformly over filings from all eras.

Interpretation and extraction notes

Several nuances matter for downstream use:

• The most analytically valuable identifier in the record is the fileNo field on the registrant entity (and any file-number references in the letter body), because it ties the RW WD to the specific Securities Act registration statement whose withdrawal is being undone. A complete event reconstruction generally requires pairing the RW WD with the prior Form RW (same file number, earlier filing date) and with the underlying S-/F-series registration statement.
• The reason for reversal is unstructured. Extracting it requires natural-language processing of the letter body, which is short but variable in phrasing across registrants and counsel. Common reason categories include tag/format corrections, strategic re-activation, and administrative error.
• Because the letter is sometimes signed by outside counsel rather than the registrant directly, the signature block is not a reliable proxy for registrant identity; the authoritative registrant identification lives in entities[*].cik and entities[*].companyName.
• Multi-registrant filings (common for shelf registrations with subsidiary co-issuers or guarantors) populate entities with multiple objects; each carries its own cik, fileNo, and role suffix, and all are bound to the same accession folder.
• The documentFormatFiles array is the most reliable inventory for programmatic extraction because it lists the on-disk filename, document type, and sequence of every attached document; iterating that array and skipping the blank-type SGML wrapper entry yields the registrant's actual submitted documents.
• Image attachments referenced inside HTML letters (via <img> tags) will resolve to missing files because graphics are excluded from the packaging; this is expected and does not indicate a corrupted record.

Who Files or Publishes This Dataset, and When

Who files the record

Form RW WD is filed by a Securities Act of 1933 registrant that previously submitted a Form RW (an application to withdraw a registration statement under Rule 477 of Regulation C) and has since decided to retract that withdrawal request. The legal filer is always the issuer/registrant whose registration statement is at issue.

The relevant filer population includes:

• Domestic operating companies registered on Forms S-1, S-3, S-4, S-8, or S-11.
• Foreign private issuers registered on Forms F-1, F-3, F-4, or F-10.
• Investment companies and BDCs registered on Forms N-2 or N-14.
• Asset-backed issuers registered on Forms SF-1 or SF-3.

The submission is typically signed by an authorized officer of the registrant (CEO, CFO, or General Counsel) or by outside counsel of record acting on the registrant's behalf. Selling stockholders, underwriters, and other parties named in the underlying registration statement are not filers.

When the record is created or required

Form RW WD is event-driven and entirely discretionary. There is no statutory or regulatory deadline. Two prerequisites must exist before a filing is possible:

1. A Securities Act registration statement (S-, F-, N-, or SF-series) is on file.
2. A Form RW under Rule 477 has been filed against that registration statement.

The trigger is the registrant's own decision to reverse the prior withdrawal request. Common reasons include a revived offering or transaction, an erroneous original RW, or a strategic preference to preserve the existing file rather than start a new registration. Filings can occur days, weeks, or months after the original Form RW.

Under Rule 477, an RW is deemed granted 15 calendar days after filing unless the staff objects. RW WDs are most often filed within that 15-day window, but registrants also submit them later where the staff can accommodate restoration of the prior registration file. Any continued activity on the original registration statement (further pre-effective amendments, pricing, or a request for effectiveness) presupposes that the RW has been reversed via RW WD.

Regulatory framework

The substantive obligation traces to the Securities Act of 1933 (Sections 5, 6, and 8) and the procedural framework of Regulation C. Rule 477 ("Withdrawal of Registration Statement or Amendment") governs the original Form RW and was amended in 1998 to introduce the 15-day deemed-grant mechanism. Form RW WD is not codified by a separate rule; it exists as an EDGAR submission type that operationalizes a registrant's reversal of a Rule 477 application.

Procedural treatment derives from:

• Regulation S-T, mandating electronic submission through EDGAR.
• the EDGAR Filer Manual, which defines RW WD as a recognized submission type and specifies tagging and routing.

Form RW WD is a procedural request addressed to the Division of Corporation Finance (or, for fund issuers, the Division of Investment Management). It contains no offering disclosure and carries no Section 11 or Section 12 liability. The submission code has been recognized on EDGAR since the early 2000s, consistent with the dataset's earliest sample date in May 2002.

Important distinctions

• Form RW vs. Form RW WD. RW is the original Rule 477 withdrawal application; RW WD reverses it. Every RW WD presupposes an existing RW for the same registration statement.
• AW (Advisers Act withdrawal on Form ADV-W) is a separate regime and is not covered by RW or RW WD.
• Form RW WD is not a registration statement amendment. Substantive changes to offering disclosure are made through pre-effective or post-effective amendments (e.g., S-1/A, F-1/A, N-2/A).
• Form RW WD is not a request for effectiveness under Section 8 or Rule 461; it only restores the registration statement to its prior procedural posture.
• Foreign private issuers and investment companies use the same RW WD submission code as domestic operating companies. There is no FPI- or fund-specific variant.
• Exchange Act-only filers, Section 13/16 reporting persons, and institutional investment managers do not file Form RW WD.
• RW WD filings are not amended through a dedicated amendment form; corrections are made via a new RW WD or correspondence with the staff.

The dataset's small size reflects the rarity of reversing a withdrawal application. RW WD is a narrow, procedural housekeeping submission tied to the lifecycle of a specific Securities Act registration statement.

How This Dataset Differs From Similar Datasets or Filings

Form RW WD is a second-order procedural submission: it reverses a prior withdrawal request and reinstates a pending Securities Act registration statement. The most useful comparisons are against the request it cancels, the registration statements it operates on, the acceleration step that often follows, and the small set of analogous "undo" filings elsewhere in EDGAR.

Form RW (Registration Withdrawal Request)

The direct counterpart. Filed under Rule 477 to withdraw a pending Securities Act registration statement before effectiveness. RW WD reverses an RW. Same filer population, same registration statement referenced, opposite intent. RW filings vastly outnumber RW WDs because most withdrawn registrations stay withdrawn. Use RW for abandonment studies; use RW WD — typically joined to the matching RW by CIK and file number — for revival studies.

Form AW and Form AW WD

Lexically similar, regulatorily distinct. AW deregisters an investment adviser under the Advisers Act of 1940; AW WD reverses an AW. AW WD shares RW WD's "withdrawal of a withdrawal" shape but applies to firm-level adviser status, not to a securities offering. Different statute, different filer population, different subject matter. The two reversal forms are conceptually parallel but content-disjoint and should never be substituted for one another.

Underlying registration statements (S-1, S-3, S-4, S-11, F-1, F-3, F-4)

These carry the actual offering disclosure — business description, risk factors, financials, prospectus. RW WD carries essentially none of that; it is a status flag. To learn what offering was reinstated, join an RW WD to the underlying registration by CIK and file number. Complementary, not substitutable.

Pre-effective amendments (S-1/A, S-3/A, F-1/A)

Both operate on a not-yet-effective registration, but amendments change what the registration says, while RW WD changes whether it remains pending at all. After an RW WD, registrants commonly file further amendments to refresh the reinstated statement. Treat them as sequential lifecycle events, not alternatives.

Rule 461 acceleration requests (CORRESP)

A Rule 461 request asks the staff to declare a registration effective at a specified time. It is typically transmitted as correspondence rather than as a standalone form, and it addresses timing of effectiveness, not the existence of the registration. RW WD restores pending status; Rule 461 decides when it goes live. Sequential, not overlapping.

Other "withdrawal of withdrawal" patterns in EDGAR

RW WD and AW WD are the two cleanly named reversal-of-reversal types. Other undo actions are scattered: Form 15 deregistrations are unwound through different filing paths rather than a dedicated "15 WD," and Schedule 13D/G changes are handled through amendments. Cross-form studies of reversed withdrawals should anchor on RW WD and AW WD and treat the rest as amendment-based.

Boundary summary

Form RW WD is bounded by three constraints that separate it from every neighbor above: Securities Act of 1933 only (not Advisers Act or Exchange Act), the reversal step only (not the original RW, the underlying registration, subsequent amendments, or acceleration correspondence), and a specific EDGAR submission type code (not analogous undo actions expressed through amendments or letters). The dataset is best used as a lifecycle marker identifying registrants who withdrew and then un-withdrew a registration. For the substance of the offering or the reasons for the reversal, it must be joined to RW filings, the underlying registration statements, pre-effective amendments, or acceleration correspondence. For the question of who executed this specific reversal and when, RW WD is the only dataset that answers it directly.

Who Uses This Dataset

Form RW WD is a narrow, high-signal filing: it reverses a prior Form RW and reinstates a registration the issuer had asked to pull. The user base is small but precise, and most workflows hinge on a handful of metadata.json fields — fileNo, accessionNo, filedAt, CIK, the filer entity name, and the letter body.

Capital markets and securities counsel

Issuer- and underwriter-side attorneys mine the dataset for precedent when a client asks whether a withdrawn registration can be revived. They read the letter text for staff-facing language and stated justifications (revived deal, new market window, restructured terms), and use fileNo to tie each RW WD back to the underlying S-1, S-3, or F-1. filedAt plus letter language reconstructs timelines for drafting their own correspondence and precedent memos.

In-house compliance and disclosure teams

Compliance staff reconcile internal registration logs against EDGAR to confirm a statement was properly reinstated and that the chain (registration -> RW -> RW WD -> post-effective amendments) is intact. CIK, accessionNo, and fileNo drive the matching; the letter confirms intent.

ECM bankers and IPO advisors

Equity capital markets teams treat each RW WD as a signal that a previously pulled deal is back in play. They pull entity name, CIK, and filedAt to flag reactivated registrations, then jump to the linked S-1 or S-3 via fileNo to assess updated size, structure, and financials. Output: pipeline dashboards, pitch material on market reopenings, competitive intelligence on returning sponsors.

IPO calendar and pipeline trackers

Specialist firms publishing IPO calendars, follow-on trackers, and shelf-status databases ingest RW WD to flip records from "withdrawn" back to "live." accessionNo is record identity, filedAt sets chronology, fileNo links to the original deal. Without this feed, their pipelines silently go stale.

EDGAR data vendors and filing-pipeline engineers

Engineering teams behind EDGAR-based products use the structured fields to drive registration-state machines and joins against S-, F-, and RW filings. The letter body feeds downstream parsing of stated reasons. The dataset supports ETL pipelines, registration-status APIs, and enrichment products marking a registration as "reinstated."

SEC staff and academic researchers

Staff researchers and academics use the full population back to May 2002 to study how often issuers reverse withdrawals, whether RW WDs cluster around market events, and what happens to reinstated offerings. They join CIK, fileNo, and filedAt with downstream S-1/S-3 outcomes to build event-study panels (priced, expired, acquired) and feed papers on IPO pipeline economics and offering behavior across market regimes.

M&A and due diligence teams

Diligence teams use RW WD records to confirm a target's true registration status. A reinstated shelf under an existing fileNo materially changes the picture, exposing buyers to undisclosed offering optionality and enabling rapid post-announcement follow-ons. They focus on entity identifiers, fileNo, and filedAt to confirm shelf availability windows.

Buy-side syndicate desks

Institutional syndicate-monitoring desks track RW WD activity to anticipate revived offerings they may be invited into. Entity, CIK, and filedAt drive watchlist updates; the linked registration informs sizing and sector exposure for pre-marketing decisions.

Quantitative researchers

Quant teams use the historical RW WD set as a discrete event flag in issuance-probability, deal-completion, and post-reinstatement performance models. filedAt, CIK, and fileNo enable joins with price, fundamentals, and filing histories for backtesting supply-pressure and event-driven strategies.

Specific Use Cases

Form RW WD records are narrow but highly actionable. The use cases below show how the metadata.json fields (fileNo, accessionNo, filedAt, CIK, companyName) and the letter body translate into concrete workflows.

Reviving an IPO/shelf pipeline tracker

Pipeline and IPO-calendar products use the monthly RW WD feed to flip registrations from "withdrawn" back to "live." Each new accessionNo is matched on fileNo to the original S-1, S-3, or F-1 already in the tracker, filedAt sets the reinstatement timestamp, and companyName plus CIK update the issuer card. Without this feed, withdrawn-then-revived deals stay incorrectly flagged as dead.

Building an RW to RW WD revival rate panel

Researchers join the full RW WD population (May 2002 to present) to the much larger Form RW corpus on CIK and fileNo to compute base rates: what fraction of withdrawn registrations are later un-withdrawn, how long the gap typically is (filedAt deltas), and which SIC codes and registration types (S-1 vs. S-3ASR vs. F-1) revive most often. The output is an event-study panel for papers and internal models on offering-pipeline behavior.

Extracting stated reasons for reversal via NLP

Analysts run text extraction over the letter body to classify why each withdrawal was undone — tag/format errors (for example S-3 mistakenly filed instead of S-3ASR), strategic re-activation, or inadvertent withdrawal. The classified reason, keyed by accessionNo, feeds dashboards distinguishing administrative noise from genuine deal-revival signals.

Reconstructing the registration-state machine in an EDGAR ETL pipeline

Filing-pipeline engineers consume RW WD as a state transition — "withdrawal-pending" back to "registration-pending" — in their EDGAR ingestion layer. fileNo is the join key against prior RW, S-/F-, and pre-effective amendment records under the same registration; filedAt orders the transitions; documentFormatFiles drives document-level extraction. The output is a clean lifecycle log per fileNo exposed through internal APIs.

Precedent search for securities counsel drafting their own RW WD

When outside counsel needs to file an RW WD for a client, they search the dataset by SIC, registration type, or stated reason to surface comparable letters — especially recent ones citing Rule 477 explicitly and reciting the "no securities sold and not declared effective" representation. The letter text and signature blocks become the precedent library; filedAt filters to recent staff-accepted phrasing.

M&A diligence on shelf availability

Diligence teams checking a target's true registration status query RW WD by CIK to detect a reinstated shelf under an existing fileNo. A live shelf materially changes deal economics by exposing the buyer to follow-on optionality, so confirming reinstatement (and pairing the filedAt against any subsequent post-effective amendments) is part of the standard pre-signing checklist.

Quant event flag for issuance-probability models

Quant researchers encode each RW WD as a discrete issuer-level event indicator keyed by CIK and filedAt, then join price, volume, and fundamental panels to test whether reinstated registrations predict near-term equity issuance, post-event drift, or supply-pressure effects. The historical depth back to 2002 supports out-of-sample backtests across multiple market regimes.

Dataset Access

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

This endpoint returns dataset metadata including the name, description, last updated timestamp, earliest sample date, total record count, total size, form types covered, container format, and content file types. It also returns the download URL for the entire dataset and the list of individual container files, with per-container size, record count, updated timestamp, and download URL. Use this endpoint to monitor which containers have changed in the most recent refresh run and decide which containers to download on a day-by-day basis. No API key is required to call this endpoint.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69c8-8e47-cf7ca3502363",
        

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

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

          5
            "description": "Form RW WD is a withdrawal of a registration withdrawal request filed under the Securities Act of 1933. It is used by registrants to reverse a previously submitted Form RW, effectively reinstating the original registration statement that was the subject of the withdrawal request. A registrant may file this submission type when withdrawal of the registration statement is no longer warranted. The dataset includes all Form RW WD filings submitted to EDGAR from May 2002 to present.",
        

          6
            "updatedAt": "2026-05-06T03:12:44.000Z",
        

          7
            "earliestSampleDate": "2002-05-01",
        

          8
            "totalRecords": 476,
        

          9
            "totalSize": 2402298,
        

          10
            "formTypes": ["RW WD"],
        

          11
            "containerFormat": "ZIP",
        

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

          13
            "containers": [
        

          14
              {
        

          15
                "downloadUrl": "https://api.sec-api.io/datasets/form-rw-wd-files/2026/2026-04.zip",
        

          16
                "key": "2026/2026-04.zip",
        

          17
                "size": 41827,
        

          18
                "records": 6,
        

          19
                "updatedAt": "2026-05-06T03:12:44.000Z"
        

          20
              }
        

          21
            ]
        

          22
          }
        

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

Downloads the complete dataset as a single ZIP archive covering all Form RW WD filings from May 2002 to the present. This endpoint requires an API key.

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

Downloads one individual monthly container ZIP rather than the full dataset, which is useful for incremental updates after a refresh run. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers EDGAR submission type RW WD — the Withdrawal of a Registration Withdrawal Request, filed under Rule 477 of the Securities Act of 1933. An RW WD reverses a previously filed Form RW and reinstates the original Securities Act registration statement that was the subject of the earlier withdrawal request.

What does one record in this dataset represent?

One record is a single complete EDGAR RW WD submission, identified by its SEC accession number and stored as a folder containing a metadata.json header plus the registrant's submitted documents (the withdrawal-reversal letter and any cover correspondence). Image files attached to the original submission are excluded from the packaging; all other documents the registrant filed are included.

Who is required to file Form RW WD?

The filer is always the Securities Act issuer/registrant whose registration statement is at issue — domestic operating companies on S-1, S-3, S-4, S-8, or S-11; foreign private issuers on F-1, F-3, F-4, or F-10; investment companies and BDCs on N-2 or N-14; and asset-backed issuers on SF-1 or SF-3. Filing is event-driven and entirely discretionary; there is no statutory deadline. The trigger is the registrant's own decision to retract a prior Rule 477 withdrawal request.

What time period does the dataset cover, and how is it refreshed?

The dataset spans the full EDGAR population of RW WD filings from May 2002 to the present. New filings are delivered through monthly ZIP containers; the dataset index JSON API exposes per-container update timestamps so consumers can identify which monthly containers have changed in the most recent refresh run.

What file format is the dataset distributed in?

Records are distributed as monthly ZIP containers. Inside each container, every record sits in a folder named after its accession number. File types found inside a record include TXT, JSON, HTML, and PDF — typically a metadata.json manifest, the SGML/TXT complete-submission wrapper, and the registrant's letter as HTML or PDF.

How does this dataset differ from the Form RW dataset?

Form RW is the original Rule 477 application to withdraw a pending Securities Act registration statement; Form RW WD reverses that request and reinstates the registration. RW filings vastly outnumber RW WDs because most withdrawn registrations stay withdrawn. Use RW for abandonment studies and RW WD — typically joined to the matching RW by CIK and fileNo — for revival studies.

How do I link an RW WD record to the underlying offering?

The most analytically valuable identifier is the fileNo field on the registrant entity inside metadata.json, which carries the SEC file number of the registration statement being addressed (for example 333-284786). Joining on CIK and fileNo ties each RW WD to the prior Form RW and to the underlying S-, F-, N-, or SF-series registration statement so the full lifecycle can be reconstructed.