The Form 1-Z-W Files Dataset is a complete collection of Regulation A withdrawal-of-exit-report filings submitted to EDGAR. Form 1-Z-W is the narrow reversal mechanism by which an issuer rescinds a previously filed Form 1-Z — the Regulation A exit report that terminates or suspends ongoing Tier 2 periodic reporting on Forms 1-K, 1-SA, and 1-U. One record in the dataset corresponds to one accession-numbered EDGAR submission by a Regulation A issuer, packaged as a metadata.json header descriptor plus the filer's original HTML withdrawal letter. The dataset covers filings from May 2017 — the earliest 1-Z-W filing date on EDGAR — to the present, distributed in ZIP containers with HTML and JSON file types. Because Form 1-Z-W is both narrow in scope and rare in practice, the dataset is used primarily by Regulation A securities counsel, issuer compliance staff, filing aggregators, auditors, and researchers who need to reconstruct which Regulation A issuers attempted to exit ongoing reporting and then reversed that decision.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset captures every Form 1-Z-W filing made on EDGAR since May 2017. Form 1-Z-W is a withdrawal request filed under Regulation A of the Securities Act of 1933, and its sole function is to rescind a prior Form 1-Z — the Regulation A exit report an issuer files to signal that it is ceasing or suspending its ongoing Tier 2 periodic reporting (Form 1-K annual reports, Form 1-SA semiannual reports, Form 1-U current event reports). By filing 1-Z-W, the issuer asks the Commission to treat the earlier 1-Z as withdrawn, which reinstates — or clarifies the continuation of — Regulation A reporting status.
Regulation A (often called Regulation A+ after the 2015 JOBS Act Title IV amendments) permits smaller issuers to conduct exempt public offerings under Tier 1 or Tier 2. Tier 2 carries ongoing periodic reporting obligations; Form 1-Z is the exit path from those obligations; Form 1-Z-W is the narrow reversal mechanism when the exit filing was premature, erroneous, or objected to by staff. As a "withdrawal of a withdrawal," the form is intentionally minimal: it does not re-establish any offering, discloses no financial information, and carries no prospectus or exhibit burden. It is in substance a short administrative letter.
Every filing in the dataset is indexed under Securities Act 33 and carries an EDGAR file number beginning with the 24R- prefix (for example 24R-00054) — the prefix EDGAR reserves for Regulation A offering files and every downstream form associated with them. The dataset is distributed as ZIP containers holding HTML submission bodies and JSON metadata descriptors; image attachments (GIF, JPG, PNG) from the original EDGAR submission are excluded per the dataset's packaging rules.
One record corresponds to one complete EDGAR filing of Form 1-Z-W. The atomic unit is an accession-level folder whose name is the 18-digit EDGAR accession number with dashes stripped (for example, accession 0001144204-18-013682 becomes folder 000114420418013682). The accession number itself decomposes as <filer-agent-CIK-zero-padded-to-10>-<2-digit-year>-<6-digit-intra-year-sequence>.
Inside that folder, the record consists of a machine-readable metadata.json header descriptor plus the original EDGAR submission documents, with image attachments removed. Because Form 1-Z-W is a deliberately minimal administrative filing, a record almost always reduces to two files: metadata.json and a single short HTML primary document, the 1-Z-W letter itself.
A record has two layers that sit side by side inside the accession folder:
metadata.json — a single flat JSON object extracted from the EDGAR SGML submission header. It is always present, always named metadata.json, and captures the cover-page / header facts that identify the issuer, the accession, the filing timestamp, and the per-document manifest.<DOCUMENT> envelope:
1
<DOCUMENT>
2
<TYPE>1-Z-W
3
<SEQUENCE>1
4
<FILENAME>tv488139_1zw.htm
5
<DESCRIPTION>1-Z-W
6
<TEXT>
7
<HTML>... body ...</HTML>
8
</TEXT>
9
</DOCUMENT>
The filer-supplied HTML filename follows no dataset-enforced scheme; it is whatever the filing agent assigned. The example tv488139_1zw.htm illustrates the typical shape: an agent-specific tracking prefix (tv488139) joined to a _1zw form-type suffix. Only metadata.json has a stable name across records.
metadata.json field shapemetadata.json is a flat object. Its top-level keys are:
formType — always the string "1-Z-W".accessionNo — the dashed 18-character accession number, e.g. "0001144204-18-013682".linkToFilingDetails — absolute URL of the primary filing document on EDGAR, in the shape https://www.sec.gov/Archives/edgar/data/<CIK>/<accession-no-dashes>/<primary>.htm.linkToTxt — URL of the complete SGML submission text file (.../<accession>.txt).linkToHtml — URL of the EDGAR filing index page (.../<accession>-index.htm).linkToXbrl — empty string; Regulation A withdrawal filings are not subject to XBRL tagging.description — short free-text description inherited from the EDGAR header, frequently terse and sometimes ending with a trailing dash (e.g. "Form 1-Z-W -").filedAt — ISO 8601 timestamp with EDGAR's eastern-time offset (e.g. "2018-03-08T18:37:59-05:00").id — opaque 32-character hexadecimal identifier assigned by the dataset.documentFormatFiles — array of per-document descriptors, one entry for each file in the original EDGAR submission plus an entry for the complete submission text file.dataFiles — empty array; Form 1-Z-W has no structured data attachments.seriesAndClassesContractsInformation — empty array; the mutual-fund series/class block never applies to Regulation A issuers.entities — array of entity descriptors; typically length one (the filer), with co-registrants appended when present.Each element of documentFormatFiles is an object with sequence, size (bytes, stringified), documentUrl, description, and type. The primary 1-Z-W HTM appears as sequence "1" with type "1-Z-W". A second entry always represents the "Complete submission text file" — the full SGML package — and its sequence and type fields are blank-space strings (" "); consumers must tolerate " " as a valid placeholder.
Each element of entities describes one filer. Relevant fields for Form 1-Z-W are:
cik — zero-padded 10-digit Central Index Key (e.g. "0001652350").companyName — legal name with an EDGAR role suffix in parentheses (e.g. "iConsumer Corp. (Filer)").type — entity role / form type, typically "1-Z-W".fileNo — EDGAR file number with the Regulation A 24R- prefix (e.g. "24R-00054").filmNo — EDGAR film number for the specific acceptance (e.g. "18677947").sic — a compound string of numeric code plus human-readable label, space-separated (e.g. "7200 Services-Personal Services").stateOfIncorporation — two-letter state code (e.g. "DE").fiscalYearEnd — MMDD fiscal-year-end marker (e.g. "1231").irsNo — IRS Employer Identification Number as a digit string (e.g. "274286597").act — Securities Act designator; always "33", because Regulation A sits under the 1933 Act.tickers — array of ticker symbols associated with the filer, non-empty when the issuer has publicly traded securities (e.g. ["RWRDP"]) and empty otherwise.Form 1-Z-W has no elaborate cover page of its own. The identifying data is carried entirely by the EDGAR SGML submission header and surfaced verbatim in metadata.json. Reconstructing the issuer from a single record therefore relies on the entities[] object rather than on parsing HTML. The combination of cik, companyName, fileNo (with its 24R- prefix), sic, stateOfIncorporation, irsNo, and fiscalYearEnd constitutes the registrant identification block that would otherwise appear on a cover page.
The file number is the structural anchor. The 24R- series is the EDGAR file-number family assigned when an issuer first qualifies a Regulation A offering on Form 1-A. Every downstream Regulation A filing by that issuer — 1-K, 1-SA, 1-U, 1-Z, and 1-Z-W — shares the same 24R- file number, which is the mechanism by which EDGAR (and consumers of this dataset) link a 1-Z-W withdrawal to the specific Regulation A offering whose exit report is being rescinded.
Form 1-Z-W does not carry a structured "prior filing" field. The linkage to the earlier Form 1-Z being withdrawn is established in two complementary ways:
24R- file number. Because EDGAR groups every filing an issuer makes against a given Regulation A offering under one file number, the prior Form 1-Z and the later Form 1-Z-W both appear under the same fileNo and cik. A consumer locates the prior 1-Z by scanning the issuer's EDGAR filing history for the most recent Form 1-Z under that file number predating the 1-Z-W's filedAt timestamp.The HTML body of a Form 1-Z-W is characteristically short — usually one short prose paragraph. The document has no rendered cover block, no signature block rendered in the body, no financial statements, no notes, no exhibits, no schedules, and no tables. Its entire substantive content is a brief statement of why the withdrawal is being made.
A representative example is the iConsumer Corp. filing (accession 0001144204-18-013682, filed 2018-03-08, document filename tv488139_1zw.htm), whose body is a single sentence:
"This 1-Z-W is being filed at the request of the staff of the Securities and Exchange Commission to clarify that the issuer does not intend to terminate Regulation A reporting."
This typifies the form's shape: a short explanation that either (a) acknowledges a staff request to rescind a prematurely or erroneously filed 1-Z, (b) clarifies the issuer intends to continue its Regulation A reporting, or (c) states some equivalent narrow administrative reason. Because the form carries no required disclosure beyond identification of the issuer and of the earlier exit report, the body can be as short as one sentence; the identifying and signer metadata lives in the SGML header surfaced through metadata.json.
Included in each record:
metadata.json — the header descriptor.<DOCUMENT> envelope.Excluded from each record:
The linkToXbrl and dataFiles fields remain empty across records; they are surfaced for schema uniformity with other EDGAR datasets rather than because Regulation A withdrawal filings have ever carried XBRL or structured data attachments.
Form 1-Z-W was introduced alongside Form 1-Z under the Regulation A+ rulemaking that took effect in June 2015. The dataset covers filings from May 2017 onward, by which time EDGAR's handling of the 24R- file-number family and the 1-Z / 1-Z-W envelope was already mature. The form's required content and structure have not changed across the dataset history: it has remained a short withdrawal letter referencing a prior Form 1-Z, with issuer identification carried by the EDGAR submission header. No new Items, new sections, or new required disclosures have been introduced.
The file format has been equally stable. Form 1-Z-W has always been filed as an HTML document wrapped in EDGAR's SGML submission envelope; it has never passed through an ASCII-only era. The file types found in the dataset are HTML for the submission body and JSON for the dataset's own metadata.json header.
entities[0].cik and entities[0].fileNo (the shared 24R- identifier) and scanning the issuer's EDGAR filing history, because the linkage is not encoded in a dedicated field.description is inherited from EDGAR and is often terse or ends with a stray trailing dash (e.g. "Form 1-Z-W -"); this reflects EDGAR header formatting and should not be treated as substantive content.documentFormatFiles, the "Complete submission text file" entry uses a single space (" ") for both its sequence and type fields. Parsers should treat blank-space strings as valid placeholders rather than errors.sic value is a compound string of numeric code followed by the SIC label; numeric-only consumers must split on the first space.entities[0].tickers may be empty or non-empty depending on whether the Regulation A issuer has publicly traded securities at the time of filing; its emptiness carries no regulatory meaning.The filer is always the Regulation A issuer itself, acting through a duly authorized officer. Each record corresponds to one EDGAR submission in which that issuer withdraws a previously filed Form 1-Z exit report.
To generate a Form 1-Z-W, an issuer must:
Typical filers are small U.S. or Canadian operating companies — the only issuer classes eligible under Rule 251(b). Entities categorically excluded from Regulation A (Exchange Act reporting companies, registered investment companies, BDCs, blank check companies, issuers of fractional undivided oil and gas interests, and issuers disqualified under Rule 262) cannot generate a Form 1-Z-W. Directors, officers, affiliates, underwriters, and selling security holders are not filers in their own capacity.
Form 1-Z-W is strictly event-driven. There is no periodic cadence, no fiscal-year tie-in, and no statutory deadline. A record exists only when one of two triggers occurs:
In both cases the filing is discretionary or prompted, not recurring. Timing is driven by when the withdrawal decision is made; filings therefore tend to appear close in time to the underlying Form 1-Z.
Form 1-Z-W is submitted electronically on EDGAR by the issuer, using the issuer's own CIK and filer credentials. The submission identifies:
024- series, commonly shown with a 24R- reference in Regulation A practice); andThe form is signed by a duly authorized officer of the issuer. Where withdrawal is prompted by staff, issuers typically coordinate with the assigned examiner beforehand, but the filing itself is always made by the issuer, not by SEC staff. The EDGAR record count for this form type begins in May 2017, the earliest filing date in the dataset.
/A variants of Form 1-Z-W are treated as separate accession-numbered records.Form 1-Z-W occupies a narrow position in the Regulation A lifecycle: it withdraws a previously filed exit report. Because it is a reversal filing, its closest neighbors fall into three groups: the exit report it undoes (Form 1-Z), the Regulation A filings it restores or is confused with by name (1-A/1-A-W and 1-K/1-SA/1-U), and other SEC withdrawal forms that share the "-W" convention but act on different underlying documents (Form 15 family, RW, AW, CB-W).
Form 1-Z is the Regulation A exit report used to terminate or suspend ongoing 1-K / 1-SA / 1-U reporting. Form 1-Z-W has a strict one-to-one referential relationship to a prior 1-Z by the same issuer: each 1-Z-W identifies the accession number of the 1-Z it pulls back. Same filer population, same regime, same EDGAR plumbing.
The difference is directional. A 1-Z marks an attempted exit; a 1-Z-W rescinds that attempt and restores the ongoing reporting obligation. A researcher who treats them as interchangeable will overstate Regulation A exits and miss the small cohort of issuers that reversed course. The 1-Z-W dataset functions as a correction layer on top of 1-Z, not an alternate view of it.
Form 1-A is the Regulation A offering statement; Form 1-A-W withdraws that offering statement before qualification is granted. The naming collision between 1-A-W and 1-Z-W is the main source of confusion, but they act at opposite ends of the lifecycle:
Conflating them mixes issuers who never launched with issuers who launched, reported, attempted to exit, and then reinstated their reporting obligation. Filer populations, counts, and economic meaning do not overlap.
1-K (annual), 1-SA (semiannual), and 1-U (current event) are the ongoing Regulation A reports that a successful 1-Z suspends and a successful 1-Z-W reinstates. They are not withdrawals and are not content-comparable to 1-Z-W; they matter as the downstream evidence of whether the reinstated obligation was actually met. A continuity study of Regulation A reporters needs 1-Z and 1-Z-W to bracket obligation state, plus 1-K/1-SA/1-U to observe compliance before and after.
Form 15 terminates or suspends Exchange Act periodic reporting (10-K / 10-Q / 8-K). It is the Exchange Act analog of Form 1-Z, not of Form 1-Z-W. EDGAR does not publish a dedicated "Form 15 withdrawal" type; issuers that wish to undo a Form 15 generally resume reporting or submit correspondence rather than a codified reversal filing. This makes 1-Z-W structurally unusual: Regulation A has an explicitly named withdrawal-of-exit form, while the Exchange Act regime does not. Researchers looking for an Exchange Act parallel will not find one, and Form 15-12B, Form 15-12G, and Form 15-15D filings must not be used as proxies for 1-Z-W events.
These share the "-W" suffix but act on different underlying filings:
A query for "all SEC withdrawal events" will return 1-Z-W alongside these, but the combined set is semantically incoherent: only 1-Z-W reverses an exit from ongoing reporting.
The Form 1-Z-W dataset is defined by three features that no other SEC dataset carries together: it is specific to Regulation A, it acts at the post-offering ongoing-reporting termination stage, and it is a reversal rather than an initiation or a periodic disclosure. Each record is interpretable only against a prior 1-Z by the same issuer. It complements the 1-Z dataset as a direct corrective layer and the 1-K/1-SA/1-U datasets as a signal of restored obligation state. It is not substitutable by 1-A-W (wrong lifecycle stage), Form 15 (wrong regime, no withdrawal counterpart), or RW/AW/CB-W (different underlying filings). For any question about Regulation A issuers that attempted to exit ongoing reporting and then reversed that decision, this dataset is the only authoritative source.
A small, specific set of professional roles consumes the 1-Z-W metadata fields (cik, fileNo with its 24R- prefix, filedAt, entityName, accessionNo) and the HTM withdrawal rationale. Across roles, the dataset converges on a narrow core: cik and entityName for identification, fileNo and prior-1-Z accessionNo for linkage, filedAt for timing, and the HTM narrative for rationale.
Lawyers drafting 1-Z-W cover letters read prior HTM narratives to see how peers justified reversal (failed Rule 257(b)(1) termination conditions, miscalculated eligibility, resumed offering activity). They pull the accessionNo of the referenced 1-Z and compare filedAt across the 1-Z and 1-Z-W to calibrate how quickly a rescission should be filed. Output: precedent-bank entry and client memo.
Compliance officers at Regulation A issuers contemplating their own rescission query by cik and entityName to locate similar filers, then read the HTM to see what continuing obligations peers acknowledged. Output: a reinstated reporting calendar for Form 1-K, 1-SA, and 1-U filings keyed off the 1-Z-W filedAt.
Staff reviewing Rule 257 and Form 1-Z mechanics use cik, filedAt, and the HTM rationale to check whether reversals cluster around specific triggers (tier transitions, offering restarts, ineligibility discoveries). Given the small record count, each filing is read individually and feeds rule-review memos.
Researchers join cik across 1-A, 1-K, 1-SA, 1-U, 1-Z, and 1-Z-W to reconstruct per-issuer event histories, using filedAt deltas to measure time between termination and reinstatement. Output: working papers on small-issuer reporting persistence.
Data engineers ingest 1-Z-W metadata to flip an issuer-status flag that would otherwise show a cik as terminated when it is back on the reporting roster. They key on cik, fileNo, filedAt, formType, and the prior 1-Z accessionNo parsed from the HTM, then re-enable expectation rules for downstream 1-K, 1-SA, and 1-U filings.
Analysts vetting a target for private placement, acquisition, or underwriting query by cik for any 1-Z, then check for a later 1-Z-W referencing that accession. The HTM narrative surfaces facts (ongoing offering, disputed eligibility, corrected prior filing) that feed the diligence report.
Litigation analysts treat a reversal as a flag that prior 1-Z representations may have been inaccurate or that offering activity continued after a claimed wind-down. cik, filedAt, and the HTM rationale populate filing-history timeline exhibits and inconsistency memos.
Auditors serving Regulation A issuers use the 1-Z-W filedAt to reset the engagement clock for the audited Form 1-K, reviewed Form 1-SA, and Form 1-U cycle. The HTM rationale is filed in workpapers as management's documented reason for reinstatement; cik and entityName tie the record to the client engagement.
Because Form 1-Z-W is a narrow reversal filing with a small filer population, its use cases are targeted and workflow-specific rather than analytical-at-scale.
Data engineers ingest each 1-Z-W's entities[0].cik and filedAt to flip an issuer's reporting status from "terminated" back to "active Regulation A reporter" in downstream databases. They reuse entities[0].fileNo (the shared 24R- identifier) to re-enable expectation rules for subsequent Form 1-K, 1-SA, and 1-U filings. Output: corrected issuer-status table and re-armed filing-deadline alerts.
Lawyers drafting a new 1-Z-W letter for a client read the HTM body of each existing filing to harvest the verbatim rationale language (for example, "filed at the request of the staff... to clarify that the issuer does not intend to terminate Regulation A reporting"). They pair each rationale with the referenced issuer's companyName, sic, and the time delta between the prior 1-Z and the 1-Z-W filedAt. Output: a precedent memo classifying reversals as staff-requested clarifications versus issuer-initiated corrections, with recommended filing timing.
Researchers join entities[0].cik and entities[0].fileNo across 1-A, 1-K, 1-SA, 1-U, 1-Z, and 1-Z-W datasets to build per-issuer event timelines. The 1-Z-W filedAt minus the prior 1-Z filedAt yields a "time-to-reversal" measure; subsequent 1-K / 1-SA cadence shows whether the reinstated obligation was actually met. Output: working-paper figures on small-issuer reporting persistence and exit-reversal incidence.
Because the dataset carries no structured back-pointer, analysts use entities[0].cik plus entities[0].fileNo (24R- prefix) to scan the issuer's EDGAR history for the most recent Form 1-Z predating the 1-Z-W's filedAt, then cross-check against the HTM body's prose reference. Output: an accession-to-accession linkage table feeding compliance workflows, litigation timelines, and due-diligence chronologies.
Analysts vetting a Regulation A issuer query by cik for any prior Form 1-Z. When a later 1-Z-W exists, they pull the HTM to determine whether the reversal was a staff-prompted correction or an issuer admission that offering activity continued past a claimed wind-down. Output: a diligence-report flag noting disputed eligibility, continued offering activity, or staff intervention history.
Auditors for Regulation A issuers use the 1-Z-W filedAt and entities[0].companyName to reset the engagement scope for the next Form 1-K audit and 1-SA review cycle that the rescinded 1-Z had previously been assumed to eliminate. The HTM rationale is filed in workpapers as management's documented reason for reinstatement. Output: updated engagement letter, revised audit plan, and workpaper documentation.
Litigation-support staff treat a 1-Z-W as a signal that prior 1-Z representations (ceasing offering, meeting Rule 257(b) conditions) may have been inaccurate. They extract cik, filedAt, and the HTM rationale, and pair them with the earlier 1-Z's assertions to build inconsistency memos and chronology exhibits. Output: timeline exhibit for staff referral or litigation filing.
The Form 1-Z-W Files Dataset is available through three access methods: a JSON index API for metadata and container listings, a single ZIP archive containing the entire dataset, and per-month container files for targeted downloads. Because the dataset is small, most users will find it simplest to download the full archive in one request.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-1zw-files.json
This endpoint returns dataset-level metadata (name, description, last update timestamp, earliest sample date, total records and size, form types covered, container format, and file types), the full dataset download URL, and the list of individual container files with per-container size, record count, updated timestamp, and download URL. It is useful for monitoring which monthly containers have changed in the most recent refresh run, so you can decide which containers to re-download on any given day. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a7f-aaea-4dc9f0106656",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-1zw-files.zip",
4
"name": "Form 1-Z-W Files Dataset",
5
"updatedAt": "2026-04-16T08:58:05.758Z",
6
"earliestSampleDate": "2017-05-01",
7
"totalRecords": 6,
8
"totalSize": 11261,
9
"formTypes": ["1-Z-W"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-1zw-files/2018/2018-03.zip",
15
"key": "2018/2018-03.zip",
16
"size": 2143,
17
"records": 1,
18
"updatedAt": "2026-04-16T08:58:05.758Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-1zw-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every monthly container. Given the dataset's small size, this is typically the most convenient option and delivers the full history in one request. This endpoint requires an API key, passed either as a ?token=YOUR_API_KEY query parameter or through an Authorization HTTP header.
Download Single Container: https://api.sec-api.io/datasets/form-1zw-files/2018/2018-03.zip?token=YOUR_API_KEY
Downloads one monthly container ZIP instead of the full dataset. Use the key values from the index response (e.g. 2018/2018-03.zip) to construct container URLs for the months you need. This endpoint requires an API key, passed either as a ?token=YOUR_API_KEY query parameter or through an Authorization HTTP header.
The dataset covers Form 1-Z-W, the Regulation A withdrawal of exit report filed under Regulation A of the Securities Act of 1933. It is the filing an issuer submits to rescind a previously filed Form 1-Z exit report, reinstating or clarifying the continuation of ongoing Tier 2 periodic reporting on Forms 1-K, 1-SA, and 1-U.
One record corresponds to one complete EDGAR filing of Form 1-Z-W, stored as an accession-level folder whose name is the 18-digit accession number with dashes stripped. Inside that folder are a metadata.json header descriptor and the original HTML 1-Z-W letter; image attachments from the EDGAR submission are excluded.
The filer is always the Regulation A issuer itself, acting through a duly authorized officer, and only after it has previously filed a Form 1-Z under Rule 257(b)(4). Typical filers are small U.S. or Canadian operating companies that qualified under Tier 2 of Regulation A. SEC staff do not file the form on the issuer's behalf, even when the withdrawal is staff-prompted.
The form is strictly event-driven with no statutory deadline or periodic cadence. It is filed either on the issuer's own initiative (to correct a premature or erroneous Form 1-Z) or at the request of SEC staff where the Rule 257(b)(4) exit conditions were not actually met.
Form 1-A-W withdraws a Regulation A offering statement before qualification, while Form 1-Z-W withdraws a post-qualification exit report. The two forms act at opposite ends of the Regulation A lifecycle and do not share filer populations or economic meaning, despite the similar "-W" naming.
The dataset does not carry a structured back-pointer. Analysts join on entities[0].cik and entities[0].fileNo (the shared 24R- Regulation A file number) and scan the issuer's EDGAR filing history for the most recent Form 1-Z predating the 1-Z-W's filedAt timestamp, then cross-check against the HTM body's prose reference.
The dataset covers filings from May 2017 — the earliest 1-Z-W filing date on EDGAR — to the present. It is distributed as ZIP containers, with HTML for the submission body and JSON for the metadata.json header descriptor; no XBRL or structured data attachments are present.