The Form 1-U Files Dataset is a curated EDGAR corpus of every Form 1-U and Form 1-U/A current-event report filed with the SEC under Rule 257(b)(4) of the Securities Act of 1933 by issuers that have qualified, or are conducting, offerings under Regulation A. Each record represents exactly one EDGAR submission — either an original Form 1-U or a Form 1-U/A amendment — keyed by its 18-digit accession number, and bundles a structured metadata.json manifest together with the verbatim HTML primary document and its preserved exhibits. Filers are Regulation A issuers (predominantly Tier 2 operating companies organized in the United States or Canada) who must disclose the triggering event within four business days. The dataset spans the entire life of Form 1-U, beginning with the earliest filings in December 2015 (shortly after the Regulation A+ rules took effect on June 19, 2015) through the present, and is delivered as monthly ZIP containers whose contents are HTML, JSON, TXT, and PDF files.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset packages Form 1-U and Form 1-U/A submissions — the Regulation A current report prescribed by Rule 257(b)(4) under the Securities Act of 1933. Form 1-U is the Regulation A counterpart to Form 8-K: a near-real-time, event-driven disclosure vehicle used between periodic reports. It was introduced by the Commission's March 2015 adopting release implementing Title IV of the JOBS Act (the "Regulation A+" amendments), became effective on June 19, 2015, and has always been an electronic-only EDGAR submission with no paper analogue.
Coverage is comprehensive with respect to the filer population: every Form 1-U and 1-U/A accepted by EDGAR from the earliest sample date of December 1, 2015 onward is included. Form 1-U and Form 1-U/A records share identical internal anatomy; the /A suffix simply marks an amendment of a previously filed current report. Each submission — original or amendment — occupies its own record with its own accession number; amendments do not overwrite originals.
The dataset is distributed as monthly ZIP containers. Inside each container, every record is a folder whose name is the dash-stripped accession number (for example, 0001640334-25-000956 becomes 000164033425000956). File types present across the corpus are HTML, JSON, TXT, and PDF; HTML and JSON dominate because virtually every Form 1-U submission consists of a metadata.json manifest plus one or more HTML documents.
A single record in the Form 1-U Files Dataset corresponds to exactly one EDGAR submission of Form 1-U or Form 1-U/A, keyed by its 18-digit EDGAR accession number. Physically, the record is a folder inside a monthly ZIP archive whose name is the dash-stripped accession number. That folder bundles two conceptually distinct layers:
metadata.json) summarising the filing header, filer identification, reportable Items, and a complete inventory of every attachment in the original EDGAR submission; and<DOCUMENT> envelope used by EDGAR.Internally, a Form 1-U submission is a short, narrowly focused disclosure document. It comprises an SEC-prescribed cover page, one or more numbered Item sections carrying the substantive disclosure, an optional exhibit index, and a signature block executed by a duly authorised officer. Because the form is single-event oriented, most filings are compact — a few pages of narrative plus any material contracts attached as exhibits — and many invoke only a single Item. The filing obligation is event-driven: once a triggering event occurs, the issuer must disclose it within four business days. The triggering events map one-to-one to the numbered Items of the form.
Each record folder carries two tiers of content:
metadata.json — a single JSON object serving as the machine-readable manifest for the submission. It encodes the EDGAR header, filer identification, the reportable Item list, and an inventory of every attachment in the original submission (including attachments that are catalogued but not materialised inside the ZIP, such as image exhibits).The minimum record is metadata.json plus a single primary .htm document. Richer records bundle several exhibit HTML documents alongside the primary. For filings whose exhibits are predominantly images, the on-disk record may contain only the HTML components while the image attachments appear only as entries in documentFormatFiles.
metadata.json manifestThe manifest is a flat JSON object. Its structured, intentional fields are:
formType — 1-U for an original current report or 1-U/A for an amendment.accessionNo — the dash-formatted EDGAR accession number (for example 0001640334-25-000956).filedAt — ISO-8601 timestamp with timezone offset recording the moment EDGAR accepted the submission.periodOfReport — the date of the triggering event, in YYYY-MM-DD form.description — a short human-readable summary, typically of the form Form 1-U - Current Report Pursuant to Regulation A - Item <N>.linkToFilingDetails — absolute sec.gov URL to the primary document.linkToHtml — URL to the EDGAR filing-index page.linkToTxt — URL to the complete SGML .txt submission bundle on EDGAR.linkToXbrl — URL to an XBRL instance when one accompanies the filing.items — array of strings naming each disclosure Item invoked by the filing (for example "Item 9.1: Other Events" or "Item 3: Material Modification to Rights of Securityholders"). This array is the most direct semantic classifier of a record.entities — array of filer records. Each entry carries cik, companyName (with a role suffix such as (Filer)), fiscalYearEnd (MMDD), stateOfIncorporation, act (Securities Act code, typically 33), fileNo (the Regulation A offering file number, for example 24R-00285), irsNo, sic (SIC code with its industry label), filmNo, type (mirroring formType), and, when the issuer has publicly traded securities, a tickers array.documentFormatFiles — ordered manifest of every attachment in the EDGAR submission. Each entry provides sequence, size in bytes, documentUrl on sec.gov, EDGAR description, and EDGAR type code. Type codes include 1-U for the primary document, exhibit codes in the EX1U-* family (for example EX1U-2A PLAN OF ACQUIS, EX1U-4 SUBS AGMT, EX1U-6 MAT CTRCT), ADD EXHB for additional exhibits, and GRAPHIC for images. A trailing entry with blank sequence and type represents the EDGAR-generated complete submission text file.seriesAndClassesContractsInformation — array reserved for series/class metadata used by investment-company filers; effectively always empty for Form 1-U issuers.dataFiles — array for structured data files; typically empty, since Form 1-U submissions rarely carry XBRL.id — stable internal hash identifier for the record.The primary filing is an HTML document wrapped in the standard EDGAR SGML envelope:
1
<DOCUMENT>
2
<TYPE>1-U
3
<SEQUENCE>1
4
<FILENAME>...1u.htm
5
<DESCRIPTION>FORM 1-U
6
<TEXT>
7
<html>... full HTML body ...</html>
8
</TEXT>
9
</DOCUMENT>
Inside <TEXT>, the rendered HTML typically presents, in order:
Cover page. The SEC-prescribed cover identifies the registrant by exact legal name, jurisdiction of incorporation, IRS Employer Identification Number, principal executive office address, and telephone number. It states the title and class of the securities issued under Regulation A and the Commission file number (a 24R-xxxxx number assigned on the underlying Form 1-A). The cover also indicates whether the submission is an original current report or an amendment.
Item heading(s) and narrative body. A bold heading introduces each numbered Item being reported, followed by a factual description of the event. Form 1-U defines the following Items:
9.1), a catch-all for voluntary disclosure of any material information the issuer elects to share.The narrative is authored prose, typically a single paragraph to a few pages, and often references attached exhibits that embody the full terms of the underlying transaction (for example a stock purchase agreement or a revised subscription agreement).
Exhibit index (optional). Many filings append an exhibit list that enumerates each attachment using Regulation A exhibit numbering (for example EX1U-2A PLAN OF ACQUIS, EX1U-4 SUBS AGMT, EX1U-6 MAT CTRCT).
Signature block. The filing closes with a dated signature, the printed name of the officer executing on the issuer's behalf, and that officer's title.
Exhibits filed with Form 1-U carry EDGAR type codes in the EX1U-* family (for example EX1U-2A plan of acquisition, EX1U-4 subscription agreement, EX1U-6 material contract), along with generic codes ADD EXHB for additional exhibits and GRAPHIC for images. HTML exhibits are preserved verbatim inside the record folder under their original EDGAR filenames (examples include ex2-1.htm, ex99_1.htm, ex0401.htm, purchaseandsale1.htm). Each exhibit HTML file is itself wrapped in an SGML <DOCUMENT> block whose <TYPE> tag names the exhibit category. The substantive content of these exhibits ranges from executed purchase-and-sale agreements and amended subscription agreements to press releases, shareholder letters, and board resolutions.
A record includes:
metadata.json manifest describing the filing header, filer entities, Item coverage, and complete attachment inventory;<DOCUMENT> envelope;<DOCUMENT> block;documentFormatFiles with its EDGAR type (typically GRAPHIC), size, description, and absolute sec.gov documentUrl, so the complete attachment inventory is always recoverable even when the binary bytes are not shipped. Filings with image-heavy exhibit sets therefore appear on disk as a small number of HTML files while the manifest enumerates a substantially larger attachment list..txt submission bundle — a single file concatenating every attachment — is not shipped in the record folder; only its URL is recorded in linkToTxt and as a trailing entry in documentFormatFiles.linkToXbrl and dataFiles are empty.fileNo (24R-xxxxx) points to, is not part of this dataset.The Item set has remained stable since adoption: Items 1 through 9 have not been restructured, and no new Items have been added. Consequently, the internal anatomy of a Form 1-U current report — cover page, Item heading, narrative, optional exhibit index, signature — is consistent across the dataset's full span from December 2015 to the present.
Two forms of structural variation nonetheless appear. First, the mix of invoked Items shifts with the Regulation A issuer base: early filings lean toward Item 1 (Fundamental Changes) and Item 8 (Unregistered Sales) as issuers execute offerings, while more recent filings tilt more heavily toward Item 9 (Other Events) as issuers use the form for voluntary material disclosure. Second, Form 1-U/A amendments may restate all, some, or none of the original Item disclosures depending on the scope of the amendment, so amendment bodies range from a narrow corrective paragraph to a near-complete re-filing.
Because Form 1-U was introduced only in mid-2015, it has never existed in the ASCII-era EDGAR format. From the earliest records onward, filings have been HTML documents wrapped in the SGML <DOCUMENT> envelope, and this convention has not materially changed. What varies is the richness of exhibit packaging: early filings tend to carry few exhibits, while more recent filings, particularly from operating Tier 2 issuers, routinely attach multi-document exhibit sets including subscription agreements, material contracts, and press releases.
accessionNo field are the canonical keys; original current reports and their 1-U/A amendments are distinct records with distinct accession numbers even when they describe the same underlying event. Reconstructing the authoritative final disclosure for an event requires joining originals with subsequent amendments on filer cik and periodOfReport.items array classifies records by reportable event with the highest fidelity; description usually echoes the same information in less structured form.entities is an array. The typical Form 1-U has a single filer, but joint filers can appear; each entity's role is annotated in parentheses within companyName (e.g. (Filer)).fileNo links to the underlying offering. The 24R-xxxxx Commission file number ties each current report to the Form 1-A offering statement that qualified the issuer under Regulation A.documentFormatFiles entry resolves to sec.gov even though the bytes are not present locally. The manifest therefore remains the authoritative attachment inventory for legal or evidentiary reconstruction..htm file begins with the EDGAR SGML <DOCUMENT> preamble (<TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT>) before the <html> body opens; downstream HTML parsers should slice from <html> onward or tolerate the preamble as prologue text.Each record is a Form 1-U or Form 1-U/A submission filed on EDGAR by a Regulation A issuer acting as a current-reporting company under Rule 257(b)(4). The issuer is the sole legal filer. Officers, directors, auditors, acquirers, and counterparties named in a Form 1-U appear as subjects of the disclosure, never as filers.
The obligation attaches only after an issuer:
Once qualified, the issuer enters the ongoing reporting regime under Rule 257 and remains subject to it until the obligation is suspended or terminated. The population is narrow:
Form 1-U is event-driven, not periodic. A filing is required only when a listed item is triggered:
A single Form 1-U may disclose multiple events under their applicable items. Exhibits (press releases, agreements, accountant letters) are attached under the exhibit index but do not themselves trigger filings.
Under Rule 257(b)(4), Form 1-U must be filed within four business days after the triggering event, mirroring the Form 8-K deadline. The clock runs from the occurrence of the event, not from the issuer's decision to disclose. Form 1-U is filed, not furnished, and becomes part of the issuer's Regulation A disclosure record. It is not used for routine earnings releases; interim financial information typically goes in Form 1-SA or a voluntary Item 9 disclosure.
Form 1-U/A amends a previously filed Form 1-U to correct, supplement, or update it, for example by later supplying financial statements of an acquired business or adding exhibits. Each Form 1-U/A is a separate EDGAR submission with its own accession number and references the original filing in its cover metadata.
Form 1-U was created by the 2015 "Regulation A+" rulemaking under Title IV of the JOBS Act of 2012 (amending Section 3(b) of the Securities Act) and became effective June 19, 2015. That rulemaking introduced the two-tier structure, the ongoing reporting regime in Rule 257, and the Regulation A reporting forms. No Form 1-U filings exist before mid-2015; the form has always been an electronic-only EDGAR submission with no paper analogue.
Within the Regulation A reporting suite, Form 1-U sits alongside:
Form 1-U sits between two disclosure regimes: the Regulation A reporting family (Forms 1-A, 1-K, 1-SA, 1-Z) and Exchange Act current reporting (Form 8-K). It is frequently confused with 8-K on mechanics and with the other Reg A forms on filer population. The comparisons below sharpen each boundary.
Form 8-K is the structural model for Form 1-U: both are event-driven, both carry a four-business-day deadline, and both share item categories including bankruptcy, change in control, principal officer departures, unregistered equity sales, and non-reliance on prior financials.
They diverge on regime and population. Form 8-K is filed under Sections 13 or 15(d) by Exchange Act reporters; Form 1-U is filed under Rule 257(b)(4) by Regulation A issuers. Rule 257(b)(4) suspends the 1-U obligation once an issuer becomes an Exchange Act reporter, so filer populations are effectively disjoint. Form 8-K's item set is also much broader — Regulation FD, material definitive agreements, ABS items, and others — none of which appear on Form 1-U. The two forms are complements across the small-issuer event landscape, not substitutes.
Form 1-A is the qualification document that must precede any Form 1-U. It is transaction-specific, long-form, narrative, filed once per offering, and contains the offering circular, financials, and exhibits. Form 1-U is short, item-based, event-triggered, and filed repeatedly after qualification. The link is chain-of-document: every 1-U filer has a qualified 1-A upstream. Use 1-A for offering terms and issuer background; use 1-U for post-qualification events.
Form 1-K is the Reg A analogue of Form 10-K: audited financials, MD&A, related-party disclosures, business description, filed within 120 days of fiscal year-end. Same filer population and same Rule 257 framework as Form 1-U, but 1-K is periodic and comprehensive where 1-U is event-driven and narrow. Events flashed through a 1-U during the year are typically restated with full financial effect in the next 1-K.
Form 1-SA is the Reg A interim report: unaudited financials and interim MD&A, filed within 90 days after the first six months of the fiscal year. Like 1-K, it is periodic and financially oriented. It may contextualize events originally disclosed on 1-U but does not carry the item-tagged current-event taxonomy (officer departures, control changes, unregistered sales) that defines 1-U.
Form 1-Z terminates Reg A reporting (or reports final Tier 1 offering status). The boundary with 1-U is temporal: 1-U filings flow throughout the active reporting window; 1-Z closes that window. After an accepted 1-Z, no further 1-U should appear. 1-A and 1-Z are the bookends; 1-K, 1-SA, and 1-U populate the interior.
Included only because Reg A and Reg CF are the two principal non-Exchange Act small-issuer regimes and are routinely conflated. The regimes do not overlap: Regulation Crowdfunding issuers file Form C, Form C-AR, and Form C-TR, and have no current-event reporting form comparable to 1-U. There is no Reg CF equivalent to Rule 257(b)(4).
Form D is a brief, typically one-page structured notice for Rule 504 and Rule 506 offerings. Regulation D imposes no ongoing current-event reporting, so there is no narrative, item-based counterpart to 1-U. Filer populations are essentially non-overlapping. The comparison matters mainly because users searching for "small-issuer event disclosure" should recognize that such disclosure effectively exists only under Regulation A, through Form 1-U.
Form 1-U is the only SEC filing that combines a four-business-day current-event trigger, a Regulation A issuer population, and an item taxonomy focused on fundamental changes, control events, officer departures, non-reliance, and unregistered equity sales. Form 8-K shares the mechanics but not the population; Forms 1-A, 1-K, 1-SA, and 1-Z share the population but are lifecycle or periodic rather than event-driven; Forms C-AR and D cover adjacent exempt-offering regimes with no current-event analogue. Within its niche — interim material events for Regulation A issuers — Form 1-U has no substitute.
Because each filing flags a discrete triggering event — fundamental changes, bankruptcy, change in control, officer departures, non-reliance on prior financials, or unregistered equity sales — Form 1-U is one of the few structured signals available on smaller exempt-offering issuers, and the user base reflects that combination of narrow regulatory scope and broad analytical interest.
Outside and in-house counsel use the corpus as a drafting precedent bank. They pull comparable Item 2 change-of-control, Item 3 bankruptcy, and Item 6 officer-departure disclosures to calibrate narrative depth, and mine attached exhibits (separation agreements, purchase agreements, receiver orders) for language patterns.
Compliance teams benchmark their own Rule 257(b)(4) practice: which fact patterns peers treated as reportable, how the four-business-day clock ran in real filings, and when 1-U/A amendments were used. Accession metadata and item flags let them reconstruct event-to-filing timelines for internal escalation playbooks.
Supervisory-principal and compliance teams at firms distributing Reg A securities monitor 1-Us from issuers on their platform for Item 5 non-reliance, Item 2 control changes, and Item 7 unregistered sales — inputs to continuing due diligence, suitability review, and FINRA-supervised customer communications.
Platform operations and legal staff ingest 1-U filings to surface item-tagged events on investor dashboards and to verify that listed issuers remain current with Rule 257 — a gating condition for continued promotion and secondary-market functionality.
Family offices, venture funds, and private-credit holders rely on Item 1 fundamental changes, Item 4 non-reliance, and Item 6 turnover disclosures to monitor positions in issuers that do not file 10-Ks or 10-Qs, feeding mark-to-model updates and investment-committee escalations.
Lower-middle-market bankers, M&A counsel, and restructuring practitioners track Item 1 and Item 2 for acquisitions and control changes absent from standard league tables, and Item 3 for receivership and bankruptcy pipelines. Exhibits supply precedent on consideration structures and plan-support terms.
Item 4 non-reliance disclosures are the primary hook: the narrative typically identifies affected periods, error type, and auditor communications. Teams build restatement-event populations in the Reg A tier and compare error and remediation patterns against reporting-company issuers.
Asset-based, venture-debt, and specialty lenders treat the dataset as an early-warning feed. Item 3, Item 5, Item 6, and Item 7 map directly onto reporting covenants and MAC clauses, supporting watchlist construction and re-underwriting.
Item 6 officer and director departures — especially resignations tied to disagreements — plus separation, consulting, and indemnification exhibits extend governance and severance benchmarks into issuers otherwise absent from standard datasets.
Law, finance, and accounting researchers use the item taxonomy and event dates to build event-study panels on Reg A post-qualification disclosure frequency, distress, and secondary-market outcomes.
Reporters covering small-cap, real estate crowdfunding, and alternative-asset issuers surface bankruptcy, abrupt CEO departures, and non-reliance events, cross-referencing 1-U filings against prior 1-A materials to identify patterns across shared sponsors or promoters.
Engineering teams normalize JSON metadata and item flags, link 1-U accessions to parent 1-A qualifications and subsequent 1-K and 1-SA reports, and generate features (event counts, inter-event time, amendment frequency) for issuer-survival and liquidity models.
Teams building retrieval systems over exempt-offering content use the corpus to test chunking, item classification, and cross-document linking across heterogeneous exhibits (HTML, PDF, text), with evaluation tasks such as extracting parties and consideration from Item 1 and Item 2 and reconciling 1-U/A amendments to originals.
Self-regulatory bodies, state securities regulators, and policy-research groups aggregate item counts, bankruptcy incidence, non-reliance frequency, and amendment rates to evaluate whether Tier 2 ongoing reporting is meeting Rule 257 investor-protection objectives.
Counsel and compliance staff anchor on item captions and narrative text; broker-dealers, platforms, credit teams, and private-market investors use item flags for ongoing exposure monitoring; M&A, restructuring, forensic, and governance practitioners mine specific items and exhibits; and academic, journalistic, engineering, and AI-development teams treat the full corpus as the structured record of the Reg A market.
Concrete workflows supported by the Form 1-U Files Dataset, grounded in metadata.json fields, the Item 1-9 narrative taxonomy, and the EX1U-* exhibit inventory.
Filter records where the items array contains "Item 5" (non-reliance on previously issued financials), then parse the primary .htm body to extract affected fiscal periods, error category, and auditor communications. Join originals with any 1-U/A amendments on entities[].cik plus periodOfReport to capture subsequent corrections. The resulting panel supports restatement-incidence research on Tier 2 issuers and comparative audit-quality studies against 10-K/A populations.
Index the primary HTML body and EX1U-* exhibits by Item, then retrieve comparable disclosures for a target fact pattern — for example, Item 6 change-of-control narratives paired with EX1U-2A PLAN OF ACQUIS attachments, or Item 7 officer departures paired with separation-agreement exhibits under ADD EXHB. Counsel use the retrieved narratives and executed exhibits to calibrate disclosure depth and re-use battle-tested contractual language.
Stream new 1-U records daily, filter on items values mapping to covenant or suitability triggers (Item 2 bankruptcy, Item 3 material modification of security-holder rights, Item 6 change in control, Item 7 officer departures), and key alerts off entities[].cik, fileNo (the 24R-xxxxx offering identifier), and any tickers. Specialty lenders use the stream to update watchlists; broker-dealers and crowdfunding platforms use it to gate continued promotion and secondary-market activity for issuers on their platform.
Pair periodOfReport (triggering-event date) with filedAt (ISO-8601 accession timestamp) across an issuer's filings to measure the lag between event and disclosure, and flag outliers exceeding four business days. Layering 1-U/A amendments on top shows correction timing and amendment frequency. Compliance teams use the output as an internal benchmarking tool; regulators and policy researchers use aggregated lags to evaluate Rule 257(b)(4) adherence across the Tier 2 population.
Select records where items contains "Item 1" (fundamental changes) or "Item 2" (bankruptcy/receivership), then extract parties, consideration, and closing conditions from the Item 1 narrative and its attached plan-of-acquisition exhibits (EX1U-2A), or trustee and plan-support details from Item 2 narratives. The output feeds M&A league tables covering Reg A transactions that typically escape mainstream deal databases, and supplies restructuring advisers with a receivership lead list keyed by sic industry and stateOfIncorporation.
Use entities[].fileNo (the 24R-xxxxx Reg A file number) and cik as join keys to connect each 1-U record to its upstream Form 1-A offering statement and its downstream Form 1-K annual and Form 1-SA semiannual reports. The chain enables issuer-level feature engineering — event counts, inter-event time, amendment rate, time-to-1-K-restatement — for survival models, liquidity analyses, and retrieval-augmented systems that need cross-document context across an issuer's full Reg A lifecycle.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-1u-files.json
This endpoint returns the dataset metadata, including name, description, last updated timestamp, earliest sample date, total records, total size, covered form types (1-U, 1-U/A), container format (ZIP), and included file types (HTML, JSON, TXT, PDF). It also provides the full-archive download URL and a list of all individual container files, each with its own key, size, record count, updated timestamp, and download URL. This endpoint does not require an API key and can be polled to monitor which containers were updated in the latest refresh run, so only changed containers need to be re-downloaded on a given day.
1
{
2
"datasetId": "1f13365b-9ae0-692e-8a62-2e23efbb7286",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-1u-files.zip",
4
"name": "Form 1-U Files Dataset",
5
"updatedAt": "2026-04-24T02:56:05.847Z",
6
"earliestSampleDate": "2015-12-01",
7
"totalRecords": 16364,
8
"totalSize": 117168715,
9
"formTypes": ["1-U", "1-U/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "JSON", "TXT", "PDF"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-1u-files/2026/2026-04.zip",
15
"key": "2026/2026-04.zip",
16
"size": 2419583,
17
"records": 42,
18
"updatedAt": "2026-04-24T02:56:05.847Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-1u-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive covering all Form 1-U and 1-U/A filings from December 2015 to the present. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-1u-files/2026/2026-04.zip?token=YOUR_API_KEY
Downloads one monthly container ZIP instead of the full dataset, which is useful for incremental updates or when only a specific period is needed. This endpoint requires an API key.
The dataset covers Form 1-U (the original current-event report) and Form 1-U/A (its amendment), the Regulation A current-reporting forms prescribed by Rule 257(b)(4) under the Securities Act of 1933. Both share identical internal anatomy; the /A suffix distinguishes amendments, which carry their own accession numbers rather than overwriting originals.
Each record represents exactly one EDGAR submission of Form 1-U or Form 1-U/A, keyed by its 18-digit accession number. Physically, a record is a folder (named after the dash-stripped accession number) containing a metadata.json manifest plus the verbatim HTML primary document and any preserved HTML, TXT, or PDF exhibits, each still wrapped in the EDGAR SGML <DOCUMENT> envelope.
Form 1-U is filed by Regulation A issuers whose offering statements on Form 1-A have been qualified by the SEC. Tier 2 Regulation A issuers (offerings up to USD 75 million in a twelve-month period) carry the full Rule 257(b) ongoing reporting burden and are the core filer group; Tier 1 issuers are generally not subject to Rule 257(b) and do not file Form 1-U. Filers are predominantly smaller U.S. and Canadian operating companies, because Regulation A requires organization and principal place of business in the U.S. or Canada.
Form 1-U must be filed within four business days after a triggering event — Items 1 through 9 of the form — occurs, mirroring the Form 8-K deadline. The clock runs from the event itself, not from the issuer's decision to disclose, and the form is filed, not furnished, so it becomes part of the issuer's permanent Regulation A disclosure record.
The dataset begins with the earliest Form 1-U filings in December 2015 — shortly after Form 1-U took effect on June 19, 2015 under the Regulation A+ rulemaking — and extends through the present. No Form 1-U filings exist before mid-2015, because the form did not exist before that date.
The dataset is delivered as monthly ZIP containers. Inside each container, every record is a folder containing metadata.json and one or more documents. Across the corpus, the file types present are HTML, JSON, TXT, and PDF, with HTML and JSON dominating; image exhibits (JPG, PNG, GIF) are deliberately omitted from the ZIP but are fully catalogued in each record's documentFormatFiles manifest with absolute sec.gov URLs.
Form 8-K is the structural model for Form 1-U — both are event-driven with a four-business-day deadline and share item categories such as bankruptcy, change in control, officer departures, unregistered equity sales, and non-reliance on prior financials — but they cover disjoint filer populations. Form 8-K is filed under Sections 13 or 15(d) of the Exchange Act by Exchange Act reporters, whereas Form 1-U is filed under Rule 257(b)(4) by Regulation A issuers; once an issuer becomes an Exchange Act reporter, Rule 257(b)(4) suspends the 1-U obligation and the issuer transitions to Form 8-K.