The Form 486A24E Files Dataset is a complete archive of Form 486A24E submissions retrieved directly from SEC EDGAR, covering filings from December 1994 onward. Each record represents a single EDGAR accession — one Form 486A24E filing made by a closed-end management investment company operating as an interval fund — and combines two registration actions in a single submission: a post-effective amendment under Securities Act Rule 486(a) and the registration of additional shares under Section 24(e) of the Investment Company Act of 1940 and former Rule 24e-2 thereunder. Records are delivered as accession-numbered directories that bundle a normalized metadata.json with the plain-text bodies of every non-image document in the original EDGAR submission. Because Rule 24e-2 was later superseded by the Rule 24f-2 indefinite share registration framework, Form 486A24E is a legacy form type and the dataset functions as a focused historical corpus of the combined Rule 486(a) plus Section 24(e) mechanism.
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 486A24E filing on EDGAR from December 1994 onward, distributed as ZIP containers holding plain-text (TXT) document bodies and per-accession JSON metadata. The underlying form is a hybrid post-effective amendment that simultaneously discharges two registration obligations under different statutes. The "486A" component refers to a post-effective amendment filed under Securities Act Rule 486(a), the reviewable lane reserved for material changes that fall outside Rule 486(b)'s safe harbors — a fundamental change in investment policy, a new share class, restructured fees, or substantive prospectus revisions. The "24E" suffix reflects that the same submission also serves as a registration of additional shares under Section 24(e) of the Investment Company Act of 1940 and former Rule 24e-2 thereunder, the legacy mechanism by which a continuously-offered fund could register additional shares on top of an existing effective registration statement once prior share registrations had been exhausted.
The body of a 486A24E submission is therefore not a free-standing form template. It is, in practice, a complete Form N-1A registration package — cover page, prospectus, statement of additional information, and Part C exhibits — re-filed as a post-effective amendment, with the cover-page captions marking it as an amendment under both the 1933 Act and the 1940 Act, accompanied by the supporting Section 24(e) counsel opinion that documents the count of additional shares being registered.
Because Rule 24f-2 absorbed essentially all routine additional-share registration activity, Form 486A24E ceased to be a routinely used form type, and the dataset is correspondingly small and concentrated in the 1990s. The structural conventions described below remain stable across the full date range; there is no later-vintage variant to account for.
One record is a single EDGAR accession — that is, one Form 486A24E submission filed by a single closed-end management investment company (typically a continuously-offered interval fund) on a specific date. Each record is materialized as an accession-number directory that bundles two layers: a normalized metadata.json describing the filing as a whole, and the set of plain-text documents that constituted the original EDGAR submission. The accession folder name is the dash-stripped, zero-padded EDGAR accession number (for example, accession 0000081247-94-000025 becomes the directory 000008124794000025), and it sits one level beneath a YYYY-MM/ folder that scopes the filing to its filing month.
Each accession directory contains:
metadata.json — a single JSON object describing the filing at the accession level: identifying attributes, the ordered list of constituent documents, and the entity (or entities) named on the filing. It is the canonical entry point for the record and is always present.document-{sequence}.txt files — one plain-text file per logical document in the original EDGAR submission, numbered to match the EDGAR sequence number assigned at submission time. Each file holds the inner payload of the corresponding EDGAR <DOCUMENT> block; the surrounding SGML wrapper has been stripped, and the metadata that lived in the wrapper (<TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>) is normalized into the matching entry of documentFormatFiles inside metadata.json. The sequence field in metadata.json is the join key back to the on-disk filename.Image files (typically GIF or JPG logos and signature scans embedded in the original SGML stream) are excluded from the on-disk payload. The concatenated full-submission .txt (the EDGAR raw SGML stream) is not materialized either — it is only referenced via linkToTxt and via a trailing documentFormatFiles entry described below.
metadata.json objectThe metadata file is a single JSON object whose primary keys describe the filing at the accession level:
formType — always "486A24E" for this dataset.accessionNo — the canonical dashed accession number (e.g., "0000081247-94-000025").id — an opaque dataset record identifier.filedAt — the ISO-8601 filing timestamp expressed in EDGAR's Eastern timezone.description — the free-text EDGAR description string carried over from the submission header (for the form generally something on the order of "Form 486A24E - Post Effective Amendments of N-2s").linkToFilingDetails, linkToTxt, linkToHtml — EDGAR Archives URLs pointing, respectively, to the filing folder, the concatenated .txt submission, and the index HTML page.linkToXbrl — an empty string for this form type.documentFormatFiles — an ordered array describing every document in the submission. Each entry exposes sequence (the integer used in the on-disk filename), type (the EDGAR document-type tag, e.g., 486A24E for the main amendment, EX-99.B6DISTRCONTR for a distributor's contract, EX-27.CLASSA for a Class A financial data schedule), description (the human-readable label assigned by the filer, e.g., "PEA#32", "24E COUNSEL OPINION", "BYLAWS"), size (a string byte count), and documentUrl (the EDGAR Archives URL). One trailing entry typically carries a blank sequence and the description "Complete submission text file"; it represents the concatenated EDGAR submission and exists only as a URL reference.entities — an array of parties on the filing. For 486A24E this is normally a single filer entity carrying cik, companyName (with a parenthetical role suffix such as "(Filer)"), type (echoing the form type), act ("40" for the Investment Company Act), fileNo (the 1933 Act file number, e.g., "002-43384"), filmNo, irsNo, stateOfIncorporation, fiscalYearEnd, and sic.seriesAndClassesContractsInformation — an array reserved for the EDGAR series/class identifier scheme. It is empty for 486A24E filings because the form predates the 2005 introduction of EDGAR series and class IDs for fund filings.dataFiles — an array reserved for structured data exhibits. It is empty for 486A24E filings.document-{n}.txt filesEach document-{n}.txt is the plain-text body of one EDGAR document with its SGML <DOCUMENT> wrapper removed. The integer n matches the sequence value of the corresponding entry in documentFormatFiles, so the type tag and human-readable description for any file can be looked up directly from metadata.json. Because 486A24E filings predate the HTML era for fund registrations, the on-disk content is overwhelmingly fixed-width ASCII — typewriter-formatted prospectus pages, exhibit text, and tabular financial schedules rendered with character-based column alignment.
The substantive content of a 486A24E accession typically organizes itself in this order. Section 24(e) anchors several of the exhibit choices, and the overall package mirrors a Form N-1A registration statement re-filed as an amendment:
486A24E, sequence 1). The substantive body of the filing, beginning with the Form N-1A cover page reproducing the Securities Act of 1933 and Investment Company Act registration captions, the post-effective-amendment number under the 1933 Act, the parallel amendment number under the 1940 Act, the pre-/post-effective-amendment checkboxes, the 1933 Act file number and 811- 1940 Act file number, and the registrant's exact legal name. The cover page is followed by:
EX-99.B2BYLAWS and similar), reproducing the trust's declaration of trust, bylaws, share certificate forms, or amendments thereto. A registrant may split these across multiple sequenced documents, each carrying the same type tag.EX-99.B9OTHCONTRCT or related), the investment advisory agreement between the fund and its adviser.EX-99.B6DISTRCONTR), the principal underwriting agreement with the fund's distributor.EX-99.B10OPINCOUNS). This exhibit is the structural anchor of the 24E portion of the form. It is a legal opinion letter that explicitly states the precise number of additional shares being registered (for example, "5,343,409 of your shares of beneficial interest") and opines on their due authorization, valid issuance, and non-assessability. It is the document that supplies the legal basis for the additional-share registration mechanism that gives the form its name, and it is the primary piece of evidence that distinguishes a 486A24E package from a plain 486APOS.EX-99.B14RETMTPLAN), where applicable, such as IRA plan documents and basic plan documents that the fund makes available to investors.EX-99.B1512B1PLAN), the Rule 12b-1 plan adopted under Section 12(b) of the 1940 Act for the relevant share class.EX-99.B16PERFQUOT), backing up the standardized yield, total return, or other performance figures shown in the prospectus.EX-27.CLASSA, EX-27.CLASSB, etc.), one per share class. EX-27 was a 1990s-era structured-financial-data exhibit format that EDGAR required for fund filings of this period; for 486A24E filings of the era they often appear as short tabular stubs prefixed with a <FLAWED> marker, which EDGAR inserted when its parser encountered a schedule it could not validate.The exact document inventory varies by registrant: a fund family with multiple share classes will produce one EX-27 schedule per class; bylaws may be split into multiple sequenced documents; share-certificate forms and additional contracts (custodian agreement, transfer-agency agreement, sub-advisory agreement) may be present or omitted; and incorporation by reference to prior filings can compress the on-disk exhibit count. The sequence ordering, however, follows the order assigned by the filer at submission and is preserved both in the on-disk filenames and in the documentFormatFiles array.
Each record packages the full text payload of every non-image document in the original EDGAR submission, plus a normalized JSON metadata layer that surfaces accession-level facts, entity identifiers, and per-document metadata that originally lived in the SGML wrappers. The Section 24(e) counsel opinion, the prospectus and SAI body, the underlying contracts, the 12b-1 plan, the performance computation, and any EX-27 financial data schedules are all retained as document-{sequence}.txt files. The trailing "Complete submission text file" entry in documentFormatFiles is preserved as a URL reference to EDGAR.
document-{n}.txt files; in 486A24E filings of this era such images are uncommon, so this exclusion rarely creates visible gaps.linkToTxt and via the trailing documentFormatFiles entry whose sequence is blank.Post-Effective Amendment No. 32 and Amendment No. 24) locate the filing inside the registrant's amendment lineage. They are extractable from the first lines of the main 486A24E document (sequence 1), not from a structured field in metadata.json.EX-99.B10OPINCOUNS counsel opinion exhibit, typically in a single sentence near the opening of the opinion ("you propose to offer and sell from time to time N of your shares of beneficial interest..."). It is not normalized into a structured metadata field.486APOS (which lacks the 24(e) additional-share component) and from a 486BPOS (which uses the immediate-effectiveness Rule 486(b) path).<FLAWED> markers inserted by the EDGAR parser, indicating that the schedule was accepted into EDGAR but failed structured validation. For downstream extraction these documents may yield empty <TABLE> stubs and should be treated as best-effort rather than authoritative financial tables; the canonical financials live in the financial-highlights and financial-statements sections of the prospectus and SAI body.documentFormatFiles entry with its own type tag (e.g., EX-27.CLASSA, EX-27.CLASSB, EX-27.CLASSM). Class-specific 12b-1 plans similarly appear as separate EX-99.B1512B1PLAN entries.document-{n}.txt to its documentFormatFiles entry on sequence, not on type. Type tags are non-unique within a single submission whenever a filer splits bylaws, share-certificate forms, or contracts across multiple sequenced documents.Each record is a post-effective amendment filed by a closed-end management investment company that operates as an interval fund. The registrant itself is the filer, acting as issuer of its own shares. Interval funds are registered under the Investment Company Act of 1940 as closed-end management investment companies, but they conduct periodic share repurchases under Rule 23c-3 and continuously offer new shares, so they need a recurring mechanism to register additional shares while keeping their registration statement current.
The filing entity is the fund vehicle itself, typically a Delaware statutory trust, Massachusetts business trust, or Maryland corporation, filing on behalf of itself and any covered series or share classes. Distributors, advisers, sub-advisers, and selling agents named in the prospectus are not filers.
A Form 486A24E filing combines two actions in one submission:
The filing is event-driven, not periodic, but in practice interval funds tended to make these amendments on an annual cadence tied to fiscal-year-end financial statement staleness rules.
Because Rule 486(a) filings are reviewable, a 486A24E does not become effective on filing. It becomes effective on the 60th day after filing unless the staff accelerates, the registrant requests acceleration, or a delaying amendment is filed. The Section 24(e) / Rule 24e-2 component required the registrant to specify the number and class of additional shares and to pay the registration fee on those incremental shares.
Rule 24e-2 was superseded by Rule 24f-2, under which registered investment companies (including interval funds) register an indefinite number of shares and pay fees in arrears based on net sales, with an annual notice on Form 24F-2. Once interval funds migrated to Rule 24f-2 indefinite registration, the need to attach a Section 24(e) share-registration component to a Rule 486(a) amendment disappeared.
Form 486A24E is therefore a legacy form type. Current interval fund post-effective amendments are filed as 486APOS, 486BPOS, or Form 486BXT, with share registration handled separately through Form 24F-2. The dataset, beginning December 1994, captures the historical window when the combined Rule 486(a) plus Section 24(e) mechanism was still in active use.
Form 486A24E sits at the intersection of Rule 486(a) post-effective amendments for closed-end interval funds and legacy Section 24(e)/Rule 24e-2 additional-share registration. The most useful comparisons are its direct Rule 486 siblings, the Rule 24f-2 framework that displaced the 24E suffix, the parent N-2 registration, the open-end 485-series analogues, and the periodic N-CSR/N-PORT reports that filers sometimes conflate with registration amendments.
Same Rule 486(a) review path, same interval-fund filer population, same 60-day default effectiveness window. The difference is share registration: Form 486APOS amends the prospectus, SAI, and exhibits without registering new shares; 486A24E adds a Section 24(e)/Rule 24e-2 share registration and the corresponding fee calculation table. Use 486APOS for ongoing prospectus updates, 486A24E when those updates are bundled with new share capacity.
The Rule 486(b) counterpart to 486APOS: immediate effectiveness, restricted to non-material categories (annual updates with audited financials, conforming or administrative edits). Same filers as 486A24E, but no SEC pre-effectiveness review and no share registration. Volumes diverge accordingly — Form 486BPOS is the routine high-frequency filing; 486A-variants are sparse because they require staff review of substantive amendments.
The closest analogue and the most likely confusion. Both bundle a Rule 486 amendment with Rule 24e-2 share registration; the split is the effectiveness path. 486B24E goes effective on filing because the amendments fit the 486(b) safe harbor; 486A24E sits in staff review because they do not. Document content (prospectus, SAI, share-count tables, fee table, exhibits) is largely identical — the choice is driven entirely by the materiality of the underlying amendments, not by the share-registration component.
The 24E suffix references former Rule 24e-2, under which funds registered a defined number of additional shares and paid the fee at registration. Rule 24f-2 replaced that mechanism with indefinite share registration and retrospective annual fee reconciliation on Form 24F-2NT based on net sales. Consequence: 486A24E and 486B24E are largely historical artifacts. Modern share-registration activity lives in 24F-2NT; 486A24E captures the older path where share registration was coupled to a specific post-effective amendment rather than reconciled annually.
The parent registration statement. Every 486A24E is a post-effective amendment to an effective N-2 (closed-end and interval funds). Form N-2 establishes the original prospectus, investment policies, fee structure, and authorized share count; 486A24E modifies that record and adds shares. Reconstructing a fund's current registration requires the original N-2 plus its full chain of Form N-2/A, 486APOS, 486BPOS, 486A24E, and 486B24E filings — N-2 is the foundation, 486A24E is one type of incremental update.
Rule 485(a) and Rule 485(b) provide the same review-required vs. immediate-effective split for open-end mutual funds and ETFs filing on Form N-1A that Rules 486(a) and 486(b) provide for closed-end interval funds on N-2. The procedural logic mirrors Form 485APOS/Form 485BPOS, but the filer populations do not overlap: open-end funds cannot file a 486-series amendment, and closed-end interval funds cannot file a 485-series amendment. There is no direct open-end counterpart to the 24E suffix because open-end share registration followed a different statutory path.
Periodic operating disclosures from the same filer universe — Form N-CSR for certified shareholder reports (financials, MD&A, auditor sign-off) and Form N-PORT for monthly portfolio holdings and risk metrics. They report on an existing fund's operation; they neither amend a registration nor register shares. Overlap is purely the filer, not the function.
Form 486A24E is defined by the convergence of four narrow attributes no other dataset combines: (1) closed-end interval funds only — not open-end, ETF, or non-interval closed-end issuers; (2) the (a) branch of Rule 486, requiring SEC pre-effectiveness review rather than immediate effectiveness; (3) the legacy Rule 24e-2 share-registration mechanism, largely displaced by the Rule 24f-2/24F-2NT regime; and (4) extreme rarity, reflecting both the narrow population and the legacy character of the 24E path. For modern share registration use 24F-2NT; for substantive interval-fund prospectus evolution use 486APOS and 486BPOS; 486A24E is uniquely fit only for the intersection of reviewable post-effective amendments and the historical 24e-2 share-registration mechanism.
Because Form 486A24E is a narrow, legacy filing path — Rule 486(a) post-effective amendments by closed-end interval funds combined with Section 24(e) / former Rule 24e-2 additional-share registration, later superseded by Rule 24f-2 — the audience is small and specialized.
Counsel advising closed-end and interval-fund sponsors use the corpus as a precedent archive for pre-24f-2 drafting. They read the cover page, Rule 486(a) invocation language, additional-share count and class, and Rule 457 fee tables inside document-N.txt, and use formType, accessionNo, filedAt, and filer CIK in metadata.json to anchor each precedent. Workflow: drafting memos on the 24e-2 to 24f-2 transition and defending interpretive positions to staff.
CCOs and registration-compliance staff at fund advisers and administrators use the dataset to reconcile the registration history of long-running interval funds. They pull share-class identifiers and registered-share counts from the prospectus and SAI sections of document-N.txt, and cross-reference accessionNo and filedAt against internal share-tracking and Blue Sky systems to tie current outstanding shares back to a complete chain of post-effective amendments.
Product structurers working on closed-end and interval-fund vehicles use the corpus as a small reference set for pre-24f-2 additional-share mechanics. They focus on the periodic-repurchase disclosure, additional-shares language, and fee tables in document-N.txt to compare historical structure against current practice when preparing internal product memos.
Share-issuance and registration-recordkeeping teams use the dataset when auditing legacy registration footprints. They extract the additional-share counts, class designations, and Rule 457 fee calculations from document-N.txt, keyed by accessionNo and filedAt in metadata.json, to reconstruct how many shares were authorized under each historical amendment.
Researchers studying the Rule 486 review framework and the 24e-2 additional-share regime use the full text of document-N.txt plus the filedAt and filer-CIK fields in metadata.json to map filing patterns and registrant identity across the entire 486A24E population. Workflow: law-review articles and casebook sections on the divergence between closed-end and open-end registration mechanics.
Analysts documenting Commission rulemaking use the dataset to trace adoption of Rule 486(a) by interval funds and the migration off 24e-2. They work from filing-date distribution and registrant identity in metadata.json and the cover-page rule citations in document-N.txt for retrospective rulemaking studies.
Engineering teams maintaining comprehensive EDGAR mirrors use the dataset as a coverage-test slice for a rare, low-volume form. They ingest metadata.json to populate filing indexes and normalize CIK and accession identifiers, and load document-N.txt into full-text stores. Workflow: regression checks confirming an internal replica handles obsolete form types.
Teams building investment-company-law assistants use the corpus as an evaluation slice. The prospectus and SAI text in document-N.txt, paired with formType and rule citations, tests whether a model can correctly identify Rule 486(a), Section 24(e), and the relationship to Rule 24f-2 from a legacy filing.
The dataset is small and historical, so use cases are narrow and concrete: legacy precedent research, registration-chain reconciliation, archival completeness, and targeted training-data slices.
Investment-company counsel pull every EX-99.B10OPINCOUNS document from each accession and extract the additional-share count sentence ("you propose to offer and sell from time to time N of your shares of beneficial interest...") together with the cover-page Rule 486(a) invocation language at the top of the sequence-1 486A24E document. Joined to accessionNo, filedAt, and the filer cik/companyName from metadata.json, this produces a per-accession table of every interval-fund 24e-2 share registration the dataset captures, useable as a drafting precedent set when responding to staff comments on legacy share-registration positions.
Fund administrators and CCOs auditing a legacy interval fund filter metadata.json records by entities[].cik to isolate that registrant's 486A24E filings, then read the post-effective-amendment numbers off the cover page of each sequence-1 document and the additional-share count from the EX-99.B10OPINCOUNS exhibit. The resulting (filedAt, PEA number, shares registered, share class) series, combined with the registrant's 486APOS, 486BPOS, and N-2 history, closes the gap between authorized-share totals on internal Blue Sky systems and the cumulative registered count under Section 24(e).
Product and contracts attorneys working on multi-class closed-end structures use the documentFormatFiles array to locate every EX-99.B1512B1PLAN, EX-99.B9OTHCONTRCT, and EX-99.B6DISTRCONTR document across the corpus, joining on sequence to load the corresponding document-{n}.txt. The resulting clause library covers distribution-fee structures, advisory agreements, and underwriting agreements as they appeared in 1990s interval-fund filings, useful when drafting modernized analogues and citing historical practice.
Data engineers maintaining a full EDGAR replica use the dataset as a regression slice for legacy SGML-era form handling. They ingest each metadata.json to confirm formType="486A24E", the dashed accessionNo format, the empty linkToXbrl, seriesAndClassesContractsInformation, and dataFiles arrays, and the trailing blank-sequence "Complete submission text file" entry, then verify that every non-trailing documentFormatFiles[].sequence resolves to a document-{sequence}.txt payload. This catches parser regressions on pre-2005 filings that lack series/class IDs and on EX-27 schedules that carry <FLAWED> markers.
Teams training or evaluating investment-company-law assistants use the corpus as a closed-set probe for legacy registration mechanics. Prompts pair formType, filedAt, and excerpts from the sequence-1 cover page or the EX-99.B10OPINCOUNS exhibit, and ask the model to identify Rule 486(a) versus 486(b), the role of Section 24(e)/Rule 24e-2, the additional-share count, and the relationship to the modern Rule 24f-2/Form 24F-2NT regime. Because the dataset's population is bounded and historical, full-coverage evaluation is tractable.
Securities-regulation academics use filedAt, entities[].cik, entities[].companyName, entities[].stateOfIncorporation, and entities[].sic across all records to map the registrant population and filing cadence of the 486A24E path from December 1994 through its decline post-Rule 24f-2. Combined with cover-page PEA numbers extracted from the sequence-1 document, the result supports law-review work on the migration off 24e-2 and the divergence between closed-end and open-end post-effective-amendment practice.
The Form 486A24E Files Dataset is accessible through three endpoints: a public dataset index JSON API for metadata, a full archive download, and per-container downloads scoped to a single month. Both download endpoints require an SEC API key, which can be passed either as an Authorization: Bearer YOUR_API_KEY header or as a ?token=YOUR_API_KEY query parameter.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-486a24e-files.json
This endpoint returns dataset-level metadata (name, description, updatedAt, earliestSampleDate, totalRecords, totalSize, formTypes, containerFormat, fileTypes), the full-archive download URL, and a list of all monthly containers. Each container entry contains its key, size, records, updatedAt, and a direct downloadUrl. Polling this endpoint is the recommended way to detect which containers were refreshed in the latest run, so only the changed months need to be fetched. This endpoint does not require an API key.
1
{
2
"datasetId": "1f13365b-9ae0-6a9a-8896-717e97768f35",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-486a24e-files.zip",
4
"name": "Form 486A24E Files Dataset",
5
"updatedAt": "2026-04-16T09:04:36.918Z",
6
"earliestSampleDate": "1994-12-01",
7
"totalRecords": 13,
8
"totalSize": 401173,
9
"formTypes": ["486A24E"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-486a24e-files/1994/1994-12.zip",
15
"key": "1994/1994-12.zip",
16
"size": 30215,
17
"records": 1,
18
"updatedAt": "2026-04-16T09:04:36.918Z"
19
}
20
]
21
}
Fetch the index with curl:
1
curl https://api.sec-api.io/datasets/form-486a24e-files.json
Or with Python:
1
import requests
2
3
index = requests.get("https://api.sec-api.io/datasets/form-486a24e-files.json").json()
4
5
print(index["name"], "-", index["totalRecords"], "records")
6
for c in index["containers"]:
7
print(c["key"], c["records"], c["updatedAt"])
Download Entire Dataset: https://api.sec-api.io/datasets/form-486a24e-files.zip?token=YOUR_API_KEY
This endpoint returns the complete dataset as a single ZIP archive covering filings from December 1994 onward. Because the dataset is small, downloading the full archive in one request is practical for most workflows. This endpoint requires an API key.
1
curl -L -o form-486a24e-files.zip \
2
"https://api.sec-api.io/datasets/form-486a24e-files.zip?token=YOUR_API_KEY"
1
import requests
2
3
url = "https://api.sec-api.io/datasets/form-486a24e-files.zip"
4
headers = {"Authorization": "Bearer YOUR_API_KEY"}
5
6
with requests.get(url, headers=headers, stream=True) as r:
7
r.raise_for_status()
8
with open("form-486a24e-files.zip", "wb") as f:
9
for chunk in r.iter_content(chunk_size=1 << 16):
10
f.write(chunk)
Download Single Container: https://api.sec-api.io/datasets/form-486a24e-files/1994/1994-12.zip?token=YOUR_API_KEY
Containers follow the YYYY/YYYY-MM.zip key pattern and hold all Form 486A24E filings submitted in that month. Use this endpoint to fetch only a specific month, for example after detecting a changed updatedAt in the dataset index. This endpoint requires an API key.
1
curl -L -o 1994-12.zip \
2
"https://api.sec-api.io/datasets/form-486a24e-files/1994/1994-12.zip?token=YOUR_API_KEY"
1
import requests
2
3
url = "https://api.sec-api.io/datasets/form-486a24e-files/1994/1994-12.zip"
4
headers = {"Authorization": "Bearer YOUR_API_KEY"}
5
6
with requests.get(url, headers=headers, stream=True) as r:
7
r.raise_for_status()
8
with open("1994-12.zip", "wb") as f:
9
for chunk in r.iter_content(chunk_size=1 << 16):
10
f.write(chunk)
The dataset covers Form 486A24E, a hybrid post-effective amendment filed by closed-end management investment companies operating as interval funds. It combines a Rule 486(a) post-effective amendment under the Securities Act of 1933 with the registration of additional shares under Section 24(e) of the Investment Company Act of 1940 and former Rule 24e-2 thereunder.
One record is a single EDGAR accession — a single Form 486A24E submission by one closed-end interval fund on one filing date. Each record is materialized as an accession-number directory holding a normalized metadata.json plus one document-{sequence}.txt per non-image document in the original EDGAR submission.
The filer is the fund vehicle itself — a closed-end management investment company operating as an interval fund, typically structured as a Delaware statutory trust, Massachusetts business trust, or Maryland corporation. Distributors, advisers, sub-advisers, and selling agents named in the prospectus are not filers. Open-end mutual funds, ETFs, traditional listed closed-end funds, and BDCs do not use this form.
The "24E" suffix references former Rule 24e-2, which required funds to register a defined number of additional shares and pay the fee at registration. Rule 24e-2 was superseded by Rule 24f-2, under which funds register an indefinite number of shares and pay fees in arrears via Form 24F-2 based on net sales. After interval funds migrated to Rule 24f-2, the combined Rule 486(a) plus Section 24(e) mechanism became unnecessary, and Form 486A24E ceased to be routinely used.
Versus 486APOS, the difference is share registration: 486APOS amends the prospectus, SAI, and exhibits without registering new shares, while 486A24E adds a Section 24(e)/Rule 24e-2 share registration and the corresponding fee calculation. Versus 486B24E, both bundle a Rule 486 amendment with Rule 24e-2 share registration, but 486B24E goes effective on filing under the Rule 486(b) safe harbor, whereas 486A24E sits in staff review under Rule 486(a) because the underlying amendments are material.
The dataset begins December 1, 1994, reflecting the phase-in of mandatory EDGAR filing for investment companies, and continues through the present. Because Rule 24f-2 absorbed routine additional-share registration activity, filings concentrate in the 1990s and the form type effectively retired thereafter.
The dataset is distributed as ZIP containers organized by filing month under the YYYY/YYYY-MM.zip key pattern. Inside each container, every accession is an accession-numbered directory containing a metadata.json and one or more document-{sequence}.txt files. The dataset surfaces only TXT and JSON file types; image files from the original SGML submissions are excluded.