The Form 8-K15D5 Files Dataset is a complete EDGAR archive of every Form 8-K15D5 and Form 8-K15D5/A submission accepted by the SEC from September 1, 1995 to the present. Each record is a single accession-number folder containing a metadata.json index plus the underlying EDGAR documents — the primary Form 8-K15D5 (or 8-K15D5/A) document, attached exhibits, and any associated XBRL data files — packaged inside monthly ZIP containers laid out as <YYYY>/<YYYY-MM>.zip. Form 8-K15D5 is the initial current report a successor issuer files under Rule 15d-5 of the Securities Exchange Act of 1934 to give public notice that it has assumed a predecessor entity's Section 15(d) periodic-reporting duty, typically following a merger, holding-company reorganization, plan of arrangement, or Chapter 11 emergence. The form is filed in the name of the successor (the new parent, surviving entity, or reorganized issuer), and amendments use the 8-K15D5/A code. Because the form is reserved for one narrow regulatory event — the migration of a Section 15(d) reporting duty — the population of records is small, and the dataset is distributed in ZIP containers that bundle TXT, JSON, and HTML 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 captures every Form 8-K15D5 and Form 8-K15D5/A filing accepted by EDGAR from September 1995 onward. Form 8-K15D5 is filed only when a successor issuer formally assumes Section 15(d) reporting obligations from a predecessor — most often as a result of a business combination, statutory merger, holding-company reorganization, share exchange, plan of arrangement, or Chapter 11 emergence — so the population is narrow by design and many filing months contain no records at all.
Each record is a single EDGAR submission identified by its 18-digit accession number. Physically, the record is a folder named after that accession number that contains a metadata.json index plus the document files that EDGAR received in the original submission: the primary Form 8-K15D5 (or Form 8-K15D5/A) document, any attached exhibits, and any associated XBRL data files. Image files (JPG, PNG, GIF) are stripped from the dataset copy; all other filed documents are preserved. Records are grouped by filing month inside ZIP containers laid out as <YYYY>/<YYYY-MM>.zip, and each accession folder is fully self-contained. The dataset is distributed as a ZIP archive containing TXT, JSON, and HTML files, reflecting the full file-format evolution of EDGAR from the ASCII/SGML era through HTML and into Inline XBRL.
Each accession folder stacks two layers of content:
metadata.json) that summarizes the filing's identity, parties, item flags, document inventory, and EDGAR cross-reference URLs.The metadata.json is always present and follows a stable schema. The document files vary in count and type from one record to another but always include the primary Form 8-K15D5 document. Across the dataset's lifespan the document files appear as plain ASCII/SGML .txt files (early era), HTML/HTM files (post-2001), and Inline XBRL XHTML files with companion XBRL schema, label, presentation, and instance documents (post-2018 cover-page tagging mandate). The file types found in the dataset are TXT, JSON, and HTML.
metadata.json indexThe metadata.json object encodes the filing's structured attributes. Its top-level fields fall into the following functional groups.
Identification. formType is either 8-K15D5 or 8-K15D5/A. accessionNo is the canonical 18-digit accession number in dash-separated form (e.g., 0000950103-25-004239). id is an internal identifier. filedAt is the EDGAR acceptance timestamp in ISO-8601 with timezone offset, and periodOfReport is the date of the reportable event (or other date the filer designated as the reporting period).
Description. A human-readable string combining the form name, an [Amend] marker for amendments, and the items checked, e.g., "Form 8-K15D5/A - Notification of assumption of duty to report by successor issue [Section 15(d)]: [Amend] - Item 5.02 Item 9.01".
Links. linkToFilingDetails points to the primary document on EDGAR (the HTM or TXT filing itself). linkToTxt points to the full submission text package that EDGAR builds by concatenating all submitted documents under SGML wrappers. linkToHtml points to the EDGAR filing-index page. linkToXbrl points to a standalone XBRL instance when one exists separately from inline XBRL; for inline-XBRL filings it is typically empty because the XBRL is embedded in the primary HTM.
documentFormatFiles. An ordered array describing each primary submission document. Each entry carries sequence (the EDGAR document sequence number), size (in bytes, as a string), documentUrl (canonical EDGAR URL), description (filer-supplied label), and type (the EDGAR document type code, such as 8-K15D5/A, EX-2.1, EX-99.1, or GRAPHIC). The first entry is normally the Form 8-K15D5 document itself; subsequent entries are exhibits and the auto-generated complete-submission .txt package.
dataFiles. An ordered array describing the XBRL data files attached to the submission. Entries cover the schema (EX-101.SCH), label linkbase (EX-101.LAB), presentation linkbase (EX-101.PRE), calculation linkbase (EX-101.CAL) when emitted, definition linkbase (EX-101.DEF) when emitted, and the extracted XBRL instance (type: XML) that EDGAR produces from the inline-XBRL primary document. The documentUrl values point to EDGAR; not all of these data files are necessarily mirrored locally into the accession folder — for many records only the primary HTM and the metadata are stored, with the full XBRL package retrievable from the URLs. For pre-2018 filings, this array is typically empty because cover-page XBRL tagging had not yet been mandated.
entities. An array with one entry per party associated with the filing. For Form 8-K15D5 records the primary entry is the successor issuer; some filings also list the predecessor entity or related parties. Each entry carries cik, companyName (suffixed with the EDGAR role label, such as "(Filer)"), fileNo (the EDGAR file number, often the predecessor's prior 333- or 001- file number that the successor inherits), filmNo, sic (the four-digit SIC code with description), stateOfIncorporation, fiscalYearEnd formatted as MMDD, act (typically "34"), type (echoing the form type as filed by that entity), and a tickers string array. The tickers array is informative for successor-issuer cases because it sometimes contains both the predecessor's pre-transaction ticker and the successor's post-transaction ticker.
items. An array of the Form 8-K item labels that were checked on the cover page, expressed as human-readable strings (e.g., "Item 5.02 Departure of Directors or Certain Officers...", "Item 9.01 Financial Statements and Exhibits"). This is the structured equivalent of the cover-page check-marks and is the most direct way to identify which Regulation 8-K disclosure obligations the filer relied on.
seriesAndClassesContractsInformation. An array reserved for fund-style series-and-class identifiers. For the operating-company filers that dominate Form 8-K15D5, this array is empty.
The primary document is the Form 8-K15D5 (or 8-K15D5/A) filing itself. Internally it follows the standard Form 8-K layout, with the structural blocks below appearing in order.
XHTML / SGML wrapper. In the modern Inline XBRL era, the primary document is an XHTML file that opens with namespace declarations for ix:, xbrli:, dei:, us-gaap:, and any filer-specific taxonomies. It is followed by an ix:header block containing ix:hidden non-numeric facts (such as dei:AmendmentFlag, dei:EntityCentralIndexKey, and dei:DocumentType), an ix:references pointer to the filer's schema (e.g., <ticker>-<period>.xsd), and an ix:resources block defining contexts (with the report period as AsOf<date>) and units (typically USD, Shares, USDPShares). In the pre-iXBRL HTML era, the wrapper is plain HTML; in the earliest ASCII era, the document is wrapped by EDGAR's SGML <DOCUMENT>...<TEXT> envelope inside a full-submission .txt package.
Cover page. A standardized header block that identifies the registrant and the type of communication. It contains:
periodOfReport.In Inline XBRL filings each of these cover-page fields is wrapped in an ix:nonNumeric element that ties the visible text to a dei: concept (entity registrant name, entity incorporation state code, entity address line, city, state, ZIP, trading symbol, security exchange name, and so on), satisfying the SEC's cover-page tagging mandate.
Explanatory Note. Form 8-K15D5/A filings, and many initial 8-K15D5s, open with a short explanatory paragraph that identifies the underlying business-combination, merger, reorganization, plan of arrangement, holding-company reorganization, chapter-11 emergence, or similar transaction that gave rise to the successor-issuer relationship. This block names the predecessor entity (or entities), the successor entity, the effective date of the transaction, and the legal basis under which the duty to report is being assumed (typically Rule 15d-5). For amendments, it also specifies what the amendment is correcting or supplementing relative to the prior filing and frequently cross-references prior 8-K15D5 filings by date.
Item-numbered disclosures. The body is organized as a sequence of Item headings drawn from the Regulation 8-K item taxonomy. Only the Items the filer checked are present; each appears as a section heading followed by narrative disclosure. The Items most commonly used in 8-K15D5 records reflect the succession context:
Each Item section is rendered as narrative HTML with embedded tables where appropriate (board-committee rosters, capital-structure tables, ownership tables). Items appear in numerical order.
Cautionary / forward-looking statement legend. Many 8-K15D5 filings include a boilerplate safe-harbor block citing Securities Act §27A and Exchange Act §21E, especially when the filing accompanies a transaction-related press release.
Signature block. The filing closes with the standardized 8-K signature block: a statement that, pursuant to the requirements of the Securities Exchange Act of 1934, the registrant has duly caused the report to be signed; the registrant's name; the date; and the signature, name, and title of the signatory (typically a senior officer such as General Counsel, Chief Financial Officer, or Corporate Secretary).
Exhibits are attached as separate documents in the EDGAR submission and are referenced by exhibit number under Item 9.01. They appear in the documentFormatFiles array of metadata.json with EDGAR document type codes such as EX-2.1, EX-3.1, EX-10.1, EX-99.1, or EX-104. The exhibit types most often seen in Form 8-K15D5 records reflect the succession-event context:
Exhibit documents are preserved in the record as filed (HTM, TXT, or XML), excluding image files.
Each record contains the metadata.json index, the primary Form 8-K15D5 (or 8-K15D5/A) document, all non-image exhibit documents that were part of the EDGAR submission, and the XBRL schema, linkbase, and instance files when those were produced as separate documents and mirrored locally. Together these reproduce both the structured facets of the filing (parties, items, dates, document inventory) and the substantive narrative and legal content of the succession notice.
<img> tags or in the documentFormatFiles array with type: GRAPHIC, but the binary files are absent. This affects only visual rendering; all textual and structural content is intact..txt (which concatenates every document under SGML wrappers) is sometimes listed in documentFormatFiles but is not always mirrored into the local accession folder; the URL in linkToTxt always points to the authoritative copy on EDGAR.For filings on or after the SEC's 2018 cover-page tagging phase-in, the primary document is an Inline XBRL XHTML file. Cover-page facts are tagged as ix:nonNumeric elements bound to dei: concepts (registrant name, incorporation state, address components, trading symbol, exchange name, emerging-growth-company flag, amendment flag, document type, and so on), and the dataFiles array carries the companion EX-101.SCH, EX-101.LAB, EX-101.PRE files plus an extracted XBRL instance and the EX-104 cover-page interactive data file. Because Form 8-K15D5 is a current-report form, only the cover page is XBRL-tagged; Item-narrative content is not numerically tagged. Pre-2018 records carry no XBRL artifacts.
The structural skeleton of Form 8-K15D5 has been stable since EDGAR began accepting it: cover page, Item-numbered narrative, signatures, exhibits. The notable evolution lies in the Item taxonomy of Regulation 8-K, which Form 8-K15D5 inherits.
metadata.json's items array.ix: namespace machinery, the ix:hidden block of DEI facts, and the EX-101.* / EX-104 data-file exhibits to the document inventory.Form 8-K15D5 filings span EDGAR's full file-format evolution, and the dataset preserves each filing in the format it was submitted.
<SEC-DOCUMENT> / <DOCUMENT> / <TEXT> envelopes inside a single full-submission .txt. Cover pages and Item narratives were rendered as monospaced text; tables were laid out with fixed-width spacing; exhibits were appended as additional <DOCUMENT> blocks within the same .txt.<DOCUMENT> block could now hold an HTM payload instead of plain text.EX-101.SCH, EX-101.LAB, EX-101.PRE, and an extracted XBRL instance, populating the dataFiles array of metadata.json.What stays constant across all three eras is the logical structure of the record: an accession-number folder, a metadata.json index, a primary Form 8-K15D5 document carrying cover page plus Item-numbered disclosures plus signatures, and exhibits attached as additional documents.
items array in metadata.json is the most reliable structured signal of what disclosures the filing carries. Combined with the Item headings inside the primary document, it allows precise routing of a record to downstream extraction logic (succession-agreement extraction from EX-2.x, board composition from Item 5.02, etc.).cik differs from the predecessor's. The entities array reflects the entity that filed; resolving the predecessor relationship typically requires reading the Explanatory Note or the EX-2.x exhibit. The tickers array sometimes captures the transition by listing both the delisted predecessor symbol and the new successor symbol.ix:nonNumeric and ix:hidden elements in the primary HTM, which is more robust than parsing the rendered HTML cover-page text.documentFormatFiles array in metadata.json, which reflects what EDGAR actually received.The filer of a Form 8-K15D5 is the successor issuer itself. The form code "15D5" tracks Rule 15d-5 under the Securities Exchange Act of 1934, which governs succession to a Section 15(d) periodic reporting duty. The successor uses Form 8-K15D5 to give EDGAR and the public formal notice that it has assumed the predecessor's Section 15(d) reporting obligation.
The filer population is narrow. Successor issuers using Form 8-K15D5 are typically:
The filing is made in the name of the successor and signed by an authorized officer (commonly the principal executive officer, principal financial officer, or another officer designated under the issuer's resolutions), consistent with Form 8-K signature requirements. Outside counsel typically drafts the filing and coordinates the EDGAR submission, but is not the filer of record.
The predecessor entity is described in the filing but is not the filer; its reporting obligation is the subject matter being transferred. After acceptance, subsequent periodic and current reports are filed by the successor under its own CIK.
Form 8-K15D5 is event-driven, not periodic. The triggering event is a succession in the Exchange Act sense: a transaction in which the assets of a Section 15(d) reporting issuer are acquired or assumed by another entity in a manner that causes the reporting obligation to pass. Common patterns:
Under Rule 15d-11 (the Section 15(d) analogue to Rule 13a-11), the filing is generally due within four business days after the triggering event. The operative event is the closing or effectiveness of the succession transaction — for example, the effective time of the merger, the effective date of the holding-company reorganization, or the effective date of the plan of reorganization. Successor issuers typically coordinate the 8-K15D5 with the closing to avoid any gap in the public reporting record.
A Form 8-K15D5/A is filed by the same successor issuer to amend a previously submitted 8-K15D5 — to complete information not available within the original four-business-day window, correct facts about the predecessor or transaction, add or revise exhibits (merger agreements, plans of reorganization), or fix identifying information. Amendments retain the legal character of the original.
The 8-K15D5 channel is reserved for successions where the inherited duty flows from Section 15(d) specifically. Adjacent channels handle other succession paths:
The predecessor's exact registration and reporting status — Section 15(d), Section 12(b), or Section 12(g) — controls which succession form is correct. Only successor issuers whose inherited duty flows from Section 15(d) appear in this dataset.
Form 8-K15D5 sits in a narrow family of successor-issuer notifications and Section 15(d) reporting events. It is most easily confused with the standard Form 8-K, with the parallel succession forms tied to Section 12, and with the larger transaction filings that surround a merger or reorganization. The comparisons below isolate the closest neighbors and pin down where 8-K15D5 is unique.
The standard 8-K is the general-purpose, recurring current report used by Section 13 or 15(d) reporting issuers to disclose material events across their entire reporting life. It shares the item-numbered structure and EDGAR pipeline of 8-K15D5. The distinction is purpose and frequency: a regular 8-K is filed many times per issuer for acquisitions, departures, results, and agreements, while 8-K15D5 is filed once, by a successor entity, solely to notify the SEC that it has inherited Section 15(d) reporting obligations from a predecessor. The 8-K15D5 dataset is therefore far smaller, structurally narrower, and tied to a specific corporate transaction rather than ongoing disclosure.
These are the direct siblings of 8-K15D5. Form 8-K12B announces succession where the predecessor's securities were registered under Section 12(b) (typically exchange-listed). Form 8-K12G3 covers Section 12(g) successions (typically OTC-registered classes). Form 8-K15D5 covers the third branch, where the predecessor's reporting obligation arose only under Section 15(d), usually from an effective registration statement rather than a registered class. The three forms map to mutually exclusive registration regimes, and the choice is dictated entirely by the predecessor's pre-succession status. Any complete study of corporate successions requires all three; substituting one for another systematically misses filers in the other regimes.
Forms 15 are the "going dark" notifications under Rule 12g-4, Rule 12h-3, and Rule 15d-6 that suspend or terminate reporting obligations at the predecessor. They are the natural counterpart to 8-K15D5: in a merger, the predecessor often files a Form 15 (15-15D, 15-12B, or 15-12G) to end its own duties while the successor files an 8-K15D5 (or 8-K12B / 8-K12G3) to acknowledge those duties have moved. Direction is the key difference — Form 15 terminates obligations at the predecessor; 8-K15D5 establishes assumption at the successor. Neither alone reconstructs the full obligation transfer.
S-4 (domestic) and F-4 (foreign private issuer) register securities issued as merger or exchange-offer consideration. They are typically filed earlier in the same transaction chain that ends with an 8-K15D5. S-4/F-4 are large narrative deal documents covering merger agreements, fairness opinions, pro forma financials, and target disclosures, oriented toward solicitation and security registration. Form 8-K15D5 is the brief administrative tail of that same transaction — a post-closing acknowledgment of a Section 15(d) duty migration. Use S-4/F-4 to study deal terms; use 8-K15D5 to identify which transactions actually produced a reporting-duty succession.
Form 10 is the long-form registration statement that establishes a full Section 12 reporting regime, with comprehensive business, financial, and risk-factor disclosure analogous to a 10-K. It sometimes mentally grouped with 8-K15D5 because both can mark an entity's entry into EDGAR reporting, but they differ fundamentally: Form 10 creates a new registration with extensive disclosure obligations at filing, whereas 8-K15D5 only notifies the SEC that an existing Section 15(d) obligation has been inherited — no new registration, no comprehensive disclosure package, and a very short document.
Form 25 notifies the SEC and the exchange that a class of securities is being delisted or removed from Section 12(b) registration, and frequently co-occurs with merger-driven successions. It operates on the listing/registration side rather than the reporting side and does not transfer ongoing reporting duties. Form 8-K15D5 says nothing about exchange listing; it concerns only the assumption of Section 15(d) reporting duties. The two may appear in the same transaction timeline but address different regulatory consequences.
Use the Form 8-K15D5 dataset when the research question concerns successor issuers that have inherited Section 15(d) reporting obligations — for example, mapping post-merger entities that continue predecessor reporting duties, building a registry of successions outside the Section 12 regime, or linking pre- and post-transaction CIKs where obligations originated from a registered offering rather than a registered class. For exchange-listed or Section 12(g) successions, use 8-K12B or 8-K12G3. For the predecessor side of the same event, pair with Forms 15-15D / 15-12B / 15-12G. For underlying deal disclosure, use S-4 or F-4. For ongoing post-succession material events at the new entity, use the standard 8-K. Form 8-K15D5 alone is narrow, transactional, and one-time; its value lies in marking the precise moment a Section 15(d) reporting duty changes hands, which no other form captures directly.
Form 8-K15D5 marks the seam where one public reporting entity gives way to another. The user base is small and technical, and each role reads different fields.
Used as a precedent library when drafting holding-company reorganizations under DGCL Section 251(g) or similar structures. Counsel mines the body narrative, the predecessor/successor identification, and the attached succession agreements, plans of merger, and charter exhibits to model their own filing. Output: drafted 8-K15D5 packages and clause libraries.
Deal lawyers confirm how successor reporting obligations have been papered historically before signing off on a target structure. They focus on predecessor and successor CIK pairs, the carried-forward file number, the form-type flag (8-K15D5 vs. 8-K15D5/A), and the cited Exchange Act recitations. Feeds closing checklists and post-closing SEC filing calendars.
Used to track successor-issuer notifications tied to Chapter 11 plan effectiveness. Practitioners look for filings linked to plan-effective dates and exhibits referencing confirmation orders or plans of reorganization. Supports post-emergence reporting calendars and confirms that registered-debt or equity reporting duties have been validly assumed.
Registrants preparing for a reorganization mine prior filings for cover-page format, item-population conventions, and exhibit indexes. Key fields are the filing header (form type, period of report, filer ID), body narrative, and exhibit list. Output: draft filing package and internal disclosure-controls memo.
Used to confirm that a deal has closed at the entity-reporting level and to map CIK/ticker continuity. The relevant fields are filing date, predecessor and successor CIKs, company names, and the triggering-transaction description. Analysts use this to rebase price, fundamental, and ownership series across the succession.
Treated as authoritative confirmation of issuer succession affecting master security files. Engineers extract the predecessor-to-successor CIK pair, the effective date, and any share-exchange or new-CUSIP references. Feeds index reconstitution logic, ETF basket adjustments, and identifier alignment across vendor systems.
Used for longitudinal studies on reorganization frequency, the prevalence of DGCL 251(g) structures, and post-succession reporting behavior. Primary inputs are full filing text, filing dates, and entity arrays across the 1995-present corpus.
Quants and knowledge-graph builders use 8-K15D5 filings as unambiguous markers of identity transitions. They consume CIKs, prior-name arrays, accession number, filing date, and predecessor references from the metadata to stitch time-aware mappings and backfill ticker, ISIN, and fundamentals histories without false continuity errors.
The corpus is small but load-bearing for any role that must capture the moment one public issuer is replaced by another: succession-drafting lawyers, restructuring counsel, disclosure teams, event-driven analysts, corporate-action engineers, researchers, and entity-resolution pipelines.
Form 8-K15D5 records are narrow but load-bearing: each one marks the precise moment a Section 15(d) reporting duty migrates from a predecessor to a successor issuer. The use cases below show concretely how the dataset is consumed.
Build a time-stamped predecessor-successor CIK map by joining the successor's cik from the entities array, the inherited Commission fileNo, and the predecessor identity parsed from the Explanatory Note and EX-2.x exhibit. The output is a CIK transition table keyed on periodOfReport that downstream pipelines use to rebase ticker, ISIN, fundamentals, and ownership histories across the succession without producing false continuity breaks.
Filter the corpus to records where the Item set includes 5.03 (charter/bylaws) and 5.02 (board), and where EX-2.x and EX-3.x exhibits indicate a Delaware holding-company reorganization. The primary 8-K15D5 narrative, succession agreement, certificate of merger, and post-reorg charter become a clause library that securities counsel reuse when drafting their own 251(g) filing package and internal disclosure-controls memo.
Identify Chapter 11-driven successions by scanning Explanatory Notes and EX-2.x exhibits for references to confirmation orders and plans of reorganization, then cross-referencing periodOfReport with the debtor's plan-effective date. Restructuring counsel and credit analysts use the result to confirm that registered-debt or equity reporting obligations were validly assumed by the reorganized issuer and to populate post-emergence SEC filing calendars.
Consume the successor cik, the inherited fileNo, the tickers array (which often contains both the delisted predecessor symbol and the new successor symbol), and the cover-page Section 12(b) securities table to drive corporate-action processing. Index and ETF data engineers feed this into reconstitution logic, basket adjustments, and identifier alignment across vendor master files so that the security record points at the correct issuer on and after the effective date.
Treat each 8-K15D5 record as an edge in a knowledge graph linking a predecessor entity node to a successor entity node, weighted by filedAt, periodOfReport, and the form-type flag (8-K15D5 vs. 8-K15D5/A). Quants and knowledge-graph builders use the resulting graph to stitch CIK, prior-name, ticker, and file-number histories into a single time-aware identity layer that other SEC datasets and market-data feeds can join against.
Event-driven and merger-arbitrage desks watch for new 8-K15D5 acceptances on EDGAR as authoritative confirmation that a merger or holding-company reorganization has closed and that the reporting duty has formally moved. The filedAt timestamp, the items array, and the cover-page registrant block are used to trigger position rebasing, mark deal completion in trade-blotter systems, and align fundamentals series with the successor CIK from that date forward.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-8k15d5-files.json
The dataset index endpoint returns a JSON document describing the Form 8-K15D5 Files Dataset and listing every container file available for download. The response includes top-level dataset metadata (name, description, earliest sample date, last updated timestamp, total records, total size, form types covered, container format, and file types) along with the full dataset download URL and a containers array. Each container entry exposes its key, size, record count, last updated timestamp, and direct download URL, which makes it straightforward to monitor daily refresh runs and selectively re-download only the containers that changed.
This endpoint does not require an API key.
1
{
2
"datasetId": "1f13365b-9ae0-6a1c-a69f-b74b3fc60335",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-8k15d5-files.zip",
4
"name": "Form 8-K15D5 Files Dataset",
5
"updatedAt": "2026-04-24T02:51:19.000Z",
6
"earliestSampleDate": "1995-09-01",
7
"totalRecords": 330,
8
"totalSize": 6673461,
9
"formTypes": ["8-K15D5", "8-K15D5/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON", "HTML"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-8k15d5-files/2025/2025-11.zip",
15
"key": "2025/2025-11.zip",
16
"size": 184213,
17
"records": 3,
18
"updatedAt": "2025-12-01T02:51:19.000Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-8k15d5-files.zip?token=YOUR_API_KEY
Downloads the complete Form 8-K15D5 Files Dataset, covering filings from 1995-09-01 onward, as a single ZIP archive. This endpoint requires a valid SEC API key from sec-api.io.
Download Single Container: https://api.sec-api.io/datasets/form-8k15d5-files/2025/2025-11.zip?token=YOUR_API_KEY
Containers are organized by year and month, with one ZIP file per month (<year>/<year>-<month>.zip). Inside each ZIP, filings are grouped into directories named by their SEC accession number, where each directory contains a metadata.json file with structured filing details alongside the original EDGAR documents (TXT, HTML, and other source files). This endpoint requires a valid SEC API key from sec-api.io.
The dataset covers Form 8-K15D5 and its amendment counterpart Form 8-K15D5/A. Form 8-K15D5 is the initial current report filed by a successor issuer under Rule 15d-5 of the Securities Exchange Act of 1934 to give public notice that it has assumed a predecessor entity's Section 15(d) periodic-reporting obligation.
One record is a single EDGAR submission identified by its 18-digit accession number, materialized as a folder containing a metadata.json index, the primary Form 8-K15D5 (or 8-K15D5/A) document, any non-image exhibits, and any associated XBRL data files. Each accession folder is fully self-contained.
The successor issuer files in its own name. Typical filers are newly formed parent holding companies in DGCL Section 251(g) reorganizations, surviving entities in mergers and consolidations, reorganized issuers emerging from Chapter 11, and successor entities in restructurings or redomiciliations — but only when the inherited duty flows from Section 15(d) specifically. Section 12(b) successions go on Form 8-K12B and Section 12(g) successions go on Form 8-K12G3.
The form is event-driven, not periodic. Under Rule 15d-11 — the Section 15(d) analogue to Rule 13a-11 — the filing is generally due within four business days of the triggering succession event (the closing or effectiveness of a merger, holding-company reorganization, plan-of-reorganization emergence, or similar transaction).
The dataset spans every Form 8-K15D5 and Form 8-K15D5/A submission accepted by EDGAR from September 1, 1995 to the present, and is refreshed on an ongoing basis as new filings are accepted. Because the form is reserved for one narrow event type, many filing months contain no records.
The dataset is distributed as ZIP containers organized by filing month at <YYYY>/<YYYY-MM>.zip. Inside each ZIP, accession-number directories hold a metadata.json index and the original EDGAR documents in TXT, HTML, and (for post-2018 filings) Inline XBRL XHTML form, along with companion XBRL schema and linkbase files where applicable. Image files are excluded.
A standard Form 8-K is a recurring current report used by an already-reporting issuer to disclose material events across its entire reporting life. Form 8-K15D5 is filed once, by a successor entity, solely to notify the SEC that it has inherited a predecessor's Section 15(d) reporting obligation. The two forms share the Item-numbered structure of Regulation 8-K, but Form 8-K15D5 is tied to a single corporate-succession event rather than to ongoing disclosure.