The Form 485BXTF Files dataset is a closed historical archive of EDGAR submissions filed under the now-retired 485BXTF submission type — Rule 485(b)(1)(iii) post-effective amendments used by registered investment companies that had elected indefinite registration under Section 24(f) of the Investment Company Act of 1940 and former Rule 24f-2 to designate a new effective date for a prior Rule 485(a) amendment. Each record represents a single EDGAR submission of submission type 485BXTF and is delivered as an accession-keyed folder containing the filing-level metadata and the as-filed document text. The submission type was active only between August 1997 and January 1998, when amendments to Rule 24f-2 adopted in Securities Act Release No. 7473 / Investment Company Act Release No. 22920 made indefinite registration automatic for open-end funds and unit investment trusts and retired the entire F-suffixed Rule 485 branch. The dataset is therefore a tiny historical specimen whose value lies in documentary completeness and in the ability to reconstruct effectiveness chains across the late-1997 / early-1998 regulatory transition rather than in volume or ongoing analytics.
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 the full EDGAR record of post-effective amendments filed on the 485BXTF submission code by Section 24(f)-electing open-end management investment companies (typically registered on Form N-1A) and unit investment trusts (registered on Form N-8B-2 with companion Securities Act registration on Form S-6, including insurance-company separate accounts issuing variable annuity or variable life contracts). The 485BXTF submission type was a narrow, election-conditioned variant within the Rule 485 family: prior to 1998, indefinite registration under Section 24(f) required an affirmative Rule 24f-2 election, and EDGAR maintained F-suffixed submission types to flag filings made under that election. The trailing F in 485BXTF flags the registrant as a Section 24(f) elector; the XT segment marks the Rule 485(b)(1)(iii) redesignation-of-effective-date variant specifically.
Coverage starts on August 1, 1997 and ends with the January 1998 retirement of the F-suffixed submission types. The dataset is closed by regulatory change rather than by sampling — no new records can ever be added. It is delivered as a ZIP archive containing per-record folders with metadata.json and plain-text document-{N}.txt files; image attachments from the original EDGAR submissions are excluded by design. Static facts about the dataset — form types covered, container format (ZIP), file types (TXT, JSON), earliest sample date, and refresh cadence — are stable; there is no XBRL content because the form predates XBRL for fund filings.
One record in the Form 485BXTF Files dataset corresponds to a single EDGAR submission of submission type 485BXTF — a post-effective amendment to a registered investment company's registration statement filed under Securities Act Rule 485(b)(1)(iii) for the narrow purpose of designating a new effective date for a post-effective amendment that had previously been filed under Rule 485(a). The trailing F flags the registrant as an entity that had elected indefinite registration of its securities under Section 24(f) of the Investment Company Act of 1940 and Rule 24f-2 thereunder. Each record is an accession-number-keyed folder containing the filing-level metadata and the full as-filed document text of that single submission, with image attachments excluded.
A 485BXTF filing is a Rule 485(b) redesignation amendment to a fund registration statement on Form N-1A (open-end management investment companies) — and, in principle, on Form N-2/Form N-3/Form N-4 for other registered investment company forms, where applicable. It does not contain a freshly drafted prospectus or statement of additional information. Its operative purpose is narrow:
F siblings in the 485 family.Functionally the filing is a short cover-and-signature instrument that hangs on, and reactivates the effective date of, an earlier filing in the registrant's amendment chain rather than a standalone disclosure document.
The dataset is delivered as a ZIP archive whose internal folder structure mirrors the filing's calendar position on EDGAR:
1
form-485bxtf-files/<year>/<year>-<month>/<accession-no-without-dashes>/
Inside each accession-keyed folder, two file types appear: a single metadata.json and one or more document-{N}.txt files, where {N} is the EDGAR document sequence number from the original submission. Image files from the original EDGAR submission are excluded by design; everything else from the raw EDGAR submission is preserved in textual form. The accession folder name is the 18-character EDGAR accession number with its two hyphens removed (for example, accession 0000837389-97-000007 becomes folder 000083738997000007), giving each record a stable primary key.
metadata.json componentmetadata.json is a flat JSON object that captures the EDGAR header- and document-level facts for the submission. The fields carry the following meaning for this form:
formType — the submission type, fixed at "485BXTF".accessionNo — the dashed EDGAR accession number, unique across all of EDGAR.description — a human-readable label, "Form 485BXTF - Post Effective Amendments to designate new effective dates".filedAt — the ISO-8601 filing timestamp with timezone offset (the filings in this dataset are timestamped at midnight Eastern, reflecting EDGAR's 1997 date-only acceptance metadata).periodOfReport — for a redesignation amendment this aligns with the filing date itself rather than a fiscal period end.linkToFilingDetails — URL to the EDGAR archive folder for the filer's CIK.linkToHtml — URL of the EDGAR -index.htm page for the filing.linkToTxt — URL of the rolled-up SGML submission text file on EDGAR.linkToXbrl — empty for every record; the form predates XBRL for fund filings.documentFormatFiles — an array of document descriptors mirroring the EDGAR <DOCUMENT> blocks. Each element carries a sequence (string), a size (string, in bytes), a documentUrl, a description (free-form, e.g. "485(B) DELAYING AMENDMENT"), and a type (mirroring the <TYPE> tag, here "485BXTF" for the primary document). The array also includes a trailing entry for the rolled-up complete submission text file, with sequence: " " and type: " "; that entry is metadata-only and does not produce its own document-N.txt in the extracted folder.entities — an array of filer descriptors, one per registrant. Each entity carries cik, companyName (with role suffix such as " (Filer)"), fileNo (the SEC file number, typically formatted 033-NNNNN for the 1933 Act registration; companion 811-NNNNN 1940 Act file numbers appear inside the document text rather than as a second entity), filmNo, act (e.g. "33"), fiscalYearEnd (a MMDD string), and type (the form type tag for that entity).seriesAndClassesContractsInformation — empty for this dataset. EDGAR's series/class identifier framework was not introduced until 2006.dataFiles — array of supplementary structured data files; empty for this dataset.id — an internal opaque identifier used by the publishing platform.The simultaneously empty linkToXbrl, dataFiles, and seriesAndClassesContractsInformation are structural rather than incidental: a 1997-vintage 485BXTF predates each of those EDGAR features, so these arrays are permanently empty and not awaiting backfill.
document-1.txt componentdocument-1.txt holds the inner body of the primary EDGAR <DOCUMENT> block as plain ASCII. The dataset strips the SGML <DOCUMENT> / <TYPE> / <SEQUENCE> / <FILENAME> / <DESCRIPTION> / <TEXT> envelope; what remains is the human-readable text of the post-effective amendment. The only EDGAR markup retained inline is the <PAGE> token, which serves as a fixed-width page-break delimiter between sections. There is no HTML, no inline XBRL, and no exhibit attachments — the form is filed as one short ASCII document formatted for monospace display.
The body is organized as a sequence of <PAGE>-separated sections in a stable, conventional order:
Cover page / file-number block — identifies the SEC file numbers (the 1933 Act 033-NNNNN registration number and the companion 1940 Act 811-NNNNN registration number), the form designation (typically FORM N-1A for open-end mutual funds), the dual-act registration assertion with checkboxes, and the post-effective amendment number under each Act. The two amendment numbers can differ — for example, Post-Effective Amendment No. 27 under the 1933 Act paired with Amendment No. 30 under the 1940 Act. The cover also names the registrant, the registrant's principal-office address and telephone number, the agent for service of process, and any "copy to" outside-counsel block.
Rule 24f-2 declaration — the structural feature that produces the F suffix. A short paragraph asserts that the registrant has previously filed a declaration pursuant to Rule 24f-2 and identifies the date and fiscal-year-end of the most recent Rule 24f-2 Notice. Without this declaration the filing would be a plain 485B, not a 485BXTF.
Effective-date election checkbox block — a four-checkbox panel specifying the operative paragraph of Rule 485 under which the amendment becomes effective: immediately upon filing under paragraph (b), on a stated date under paragraph (b), 60 days after filing under paragraph (a), or on a stated date under paragraph (a). For 485BXTF the checked option is the dated paragraph (b) line, with the new effective date written in. This checkbox block is what makes the filing a Rule 485(b) instrument as opposed to a Rule 485(a) substantive amendment.
Cross-reference sheet (Parts A, B, C) — a multi-page, two-column mapping between the enumerated Items of the underlying registration form (Form N-1A) and the captions in the registrant's prospectus, statement of additional information, and other-information sections. Part A maps Items 1–9 to prospectus captions; Part B maps Items 10–23 to SAI captions; Part C lists Items 24–32 (financial statements and exhibits, persons under common control, indemnification, business and other connections of investment advisers, principal underwriter, location of accounts and records, management services, undertakings) without a captions column. The cross-reference sheet preserves the canonical Form N-1A item structure even though the substantive disclosure content is not re-filed.
Incorporation-by-reference statement — a one-paragraph block in which the registrant explicitly incorporates by reference the Prospectus (Part A), Statement of Additional Information (Part B), and Other Information (Part C) content filed in the prior Rule 485(a) post-effective amendment. The paragraph names the prior amendment by its post-effective amendment number and its filing date. This is the operative substantive content of the filing — every other section supports this incorporation and the redesignation of the effective date.
Signature block — opens with the Rule 485(b) certification language ("the Registrant certifies that it meets all of the requirements for effectiveness of this Registration Statement pursuant to Rule 485(b)"), restates the dual amendment numbers, and gives the city, state, and date of execution. It then carries the registrant's signature line under its corporate name, the principal executive officer's signature, the principal accounting officer's signature, and the directors' signature lines. Director signatures are commonly executed via attorney-in-fact under a previously filed power of attorney, with an asterisk-marked footnote pointing to the post-effective amendment in which the powers of attorney were filed.
Each record contains:
metadata.json describing the submission's EDGAR header facts, document inventory, filer entities, and filing-level URLs.document-{N}.txt files keyed to the EDGAR sequence number. For 485BXTF this is in practice a single document-1.txt containing the cover, Rule 24f-2 declaration, Rule 485(b) effective-date election, cross-reference sheet, incorporation-by-reference paragraph, and signature block.<DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT>) are not preserved around the document body; only the inner text and inline <PAGE> markers remain. The header facts that those tags would carry are mirrored in metadata.json.documentFormatFiles is a metadata pointer to the rolled-up SGML submission on EDGAR and does not produce a separate document-N.txt file in the extracted folder.Two orthogonal axes structured the pre-1998 485 family:
485A* types covered Rule 485(a) substantive amendments that became effective only after SEC review; 485B* types covered Rule 485(b) amendments that became effective automatically on a specified date for limited categories of changes, including redesignation under paragraph (b)(1)(iii). The XT segment marked the redesignation-of-effective-date variant specifically.485A24E and 485B24E (used by registrants that had elected indefinite registration under Rule 24f-2). The F-suffixed forms — including 485BXTF — sat in the same election-flagged group.When the January 1998 Rule 24f-2 amendments collapsed the election distinction, the F and 24E variants were removed from the form list, and Rule 485 amendment activity collapsed into the surviving 485APOS and 485BPOS types, with 485BXT continuing to play the redesignation role for filers who needed it. This dataset captures a thin slice at the very end of that prior regime.
metadata.json for filing-level facts and document-1.txt for the as-filed text. Higher-order disclosure structure (Parts, full Items, exhibits, financial statements, notes) is not present in the body of a 485BXTF because the form's regulatory function is redesignation rather than disclosure.File Nos. header, FORM N-1A, Post-Effective Amendment No., Rule 24f-2, pursuant to paragraph (b), incorporates by reference, and the certification opening of the signature block — with <PAGE> markers serving as section boundaries.linkToXbrl, dataFiles, and seriesAndClassesContractsInformation are permanent properties of every record in the dataset, reflecting the 1997 vintage of the filings and the pre-XBRL, pre-series/class-tagging state of EDGAR at that time.Each record is a post-effective amendment filed on EDGAR by a registered investment company that had elected indefinite registration of its securities under Section 24(f) of the Investment Company Act of 1940 and former Rule 24f-2 thereunder. In practice, the filer population is limited to:
Closed-end funds, business development companies, and operating companies are outside the Rule 485 framework entirely and do not appear in this dataset. Open-end funds and UITs that registered a definite number of shares (and therefore did not make the Section 24(f) election) used the non-"F" Rule 485 variants and are also excluded. The trailing "F" suffix in the submission type identified the Section 24(f) "F" branch of EDGAR's Rule 485 submission types.
The legal filer is the registrant entity — the trust, corporation, series company, or UIT — identified on EDGAR by its CIK. For UIT-based insurance products, the filer is typically both the separate account (UIT registrant under the 1940 Act) and the depositor insurance company (1933 Act issuer of the contracts), and both CIKs may appear on the submission.
Form 485BXTF is event-driven, not periodic. It exists to carry out the effective-date redesignation mechanism in Securities Act Rule 485(b)(1)(iii) for Section 24(f) "F" registrants.
Two conditions must be present:
There is no calendar deadline. The redesignation must simply occur within the Rule 485 framework — before the underlying 485(a) amendment is superseded or withdrawn — and must satisfy the conditions of Rule 485(b)(1)(iii).
Form 485BXTF has an unusually narrow life. Filings of this type appear on EDGAR only between August 1997 and January 1998. The submission code was retired when the Commission adopted amendments to Rule 24f-2 in Securities Act Release No. 7473 / Investment Company Act Release No. 22920 (adopted late 1997, effective in early 1998). Those amendments made indefinite registration of open-end fund and UIT shares automatic and eliminated the separate Section 24(f) election, which in turn eliminated the rationale for bifurcating Rule 485 submission types into "F" and non-"F" branches. The entire "F" branch — 485APOSF, 485BPOSF, 485BXTF, 485A24E, 485B24E — was discontinued. Because the submission type ran for only a few months and existed entirely within the EDGAR era, the EDGAR record set is effectively the complete record set, and no new records will ever be added.
After January 1998, any equivalent effective-date redesignation activity migrated to the surviving non-"F" Rule 485 family (principally 485BPOS) and is not part of this dataset.
Filer vs. signers. Officers, trustees, directors, the principal underwriter, and the investment adviser may be named or sign the amendment, but they are not the filers. The registrant is.
Pairing with the underlying amendment. A 485BXTF record does not stand alone in substance. It points back to a prior 485APOSF and merely fixes its effective date; reconstructing the underlying disclosure changes requires pairing the 485BXTF with the earlier 485APOSF in the registrant's EDGAR history.
Excluded populations. Closed-end management investment companies, business development companies, and operating-company issuers never used Rule 485. Open-end funds and UITs that had not made the Section 24(f) election used the non-"F" Rule 485 variants. None of these appear in the dataset.
No post-1998 amendments under this code. Because the submission type was retired, there are no later 485BXTF amendments. Any subsequent corrections to a late-1997 redesignation were carried forward through the post-1998 Rule 485 framework under different submission codes.
Form 485BXTF sits in a tightly defined neighborhood of post-effective amendments to investment company registration statements. To place it precisely, it must be distinguished along four axes: the Rule 485(a) vs. Rule 485(b) split, the now-retired Section 24(f) "F"-suffix family, the parallel Rule 24e-2 "24E" family, and the underlying registration statements (N-1A, N-8B-2) plus Rule 497 prospectus filings. Each is adjacent in statutory mechanics, filer population, or document flow, and each is easy to conflate with 485BXTF if the rule citations slip.
Form 485APOS (Rule 485(a)). The substantive amendment vehicle. A 485APOS carries the marked-up registration statement and prospectus changes, and triggers the default 60-day staff review window before automatic effectiveness under Rule 485(a)(2) (75 days for certain newly added series). 485BXTF is its downstream counterpart: it redesignates the effective date of a previously filed 485(a) amendment under Rule 485(b)(1)(iii), and carries only a cover page, the new effective date, signatures, and any required exhibits. The two are sequential, not substitutable.
Form 485BPOS (Rule 485(b)). The immediately effective post-effective amendment for ministerial Rule 485(b)(1) updates — annual financial updating, certain non-material changes — that bypass staff review. 485BXTF is mechanically a sub-species of 485(b), authorized specifically by Rule 485(b)(1)(iii), the subparagraph reserved for redesignation of a prior 485(a) effective date. The dividing line is therefore both the narrower rule subparagraph and the additional 24(f)-election overlay (the "F") plus redesignation tag ("XT").
Forms Form 485APOSF and Form 485BPOSF. The "F"-suffix counterparts to 485APOS and 485BPOS, used by registrants that had affirmatively elected indefinite registration under Section 24(f) and Rule 24f-2 as it stood before its 1997 amendment. 485BXTF is to 485APOSF what 485BPOS is to 485APOS, but narrowed to the single function of redesignating an effective date. 485BPOSF carries substantive Rule 485(b)(1) updates by a 24(f) elector; 485BXTF carries only the redesignation of a prior 485APOSF.
Forms Form 485A24E and Form 485B24E. The Rule 485(a) and 485(b) variants for funds operating under the older Rule 24e-2 definite-share annual update regime — registrants that had not elected Section 24(f) and instead registered a definite number of shares each year. The 24E and 24F suffixes mark mutually exclusive quantity regimes: definite-share under Rule 24e-2 versus indefinite under a Rule 24f-2 election. There is no "24E" analogue of the "XT" redesignation tag; 485BXTF is exclusively a 24(f)-elector instrument.
Form N-1A. The combined Securities Act / Investment Company Act registration statement for open-end management investment companies. All 485-series amendments operate on an existing N-1A. The relationship is hierarchical: N-1A is the base; 485APOS / 485APOSF amends it substantively; 485BXTF merely sets the date on which a prior 485(a) amendment to that N-1A becomes effective. 485BXTF adds no N-1A disclosure of its own.
Form N-8B-2. The registration statement for unit investment trusts (paired historically with S-6 on the Securities Act side). UITs that had elected Section 24(f) also used the F-suffix 485 amendments and could therefore file 485BXTF. The relationship mirrors the N-1A case: 485BXTF redesignates the effective date of a prior 485(a) amendment to a UIT registration statement without itself constituting a new registration or substantive amendment.
Rule 497 prospectus filings. Submission types 497, 497K, 497J and related variants deposit definitive prospectuses, summary prospectuses, and supplements after a registration statement is effective. They are commonly confused with 485 amendments because both touch fund prospectus material, but they are legally distinct: Rule 497 lodges the as-used document; Rule 485 amends the registration statement. 485BXTF is purely a 1933 Act post-effective amendment and contains no Rule 497 prospectus; neither can substitute for the other.
Three features separate 485BXTF from every neighbor above:
The Form 485BXTF Files dataset is a tightly bounded historical artifact: post-effective amendments filed in the brief window before Rule 24f-2's January 1998 reform, by Section 24(f)-electing open-end funds and UITs, whose sole purpose was to set a new effective date for a previously filed Rule 485(a) amendment. It does not substitute for a 485APOS / 485APOSF dataset (substantive disclosure), a 485BPOS / 485BPOSF dataset (immediately effective Rule 485(b)(1) updates), a Rule 497 dataset (as-used prospectus documents), or an N-1A / N-8B-2 dataset (base registration). It is best used alongside a Form 485APOSF dataset, where each 485BXTF accession pinpoints the redesignation event for an earlier 485(a) filing in the same pre-1998 amendment chain. Outside that linkage and that window, no other EDGAR submission type performs the same function.
The audience for the Form 485BXTF Files dataset is narrow and almost entirely documentary, reflecting the form's status as a frozen specimen of a discontinued submission type.
Lawyers and historians tracing the evolution of Rule 24f-2 and Section 24(f) cite this filing as primary-source evidence of the pre-1998 indefinite-registration election regime. The "F" suffix marks a registrant that affirmatively elected Section 24(f) treatment, so the cover-page identification and the explicit Rule 485(b)(1)(iii) and Rule 24f-2 references are what matter. The record supports treatise updates, expert reports, and memoranda showing the procedural shape the 1998 amendments rendered obsolete.
Compliance officers at long-operating fund complexes use the record to close a specific gap in a registrant's chain across the 1997-1998 transition. They look at the registrant identifier and prior-PEA reference, the newly designated effective date under Rule 485(b)(1)(iii), and the officer signatures. The output is an internal registration-history database entry or an audit response demonstrating continuous prospectus effectiveness.
In disputes over fund share issuances in late 1997 or early 1998 — rescission claims, alleged prospectus defects, share-class history questions — a 485BXTF redesignation can be a necessary link in proving an unbroken effectiveness chain. The redesignation language, prior-PEA reference, and new effective date are the evidentiary fields. The filing is used as an authenticated EDGAR-source exhibit, not as analytical input.
Data engineers responsible for mirroring every submission type that has ever appeared on EDGAR include 485BXTF for coverage. Their concern is that the form type is recognized, accession numbers resolve, and metadata plus document files are retrievable. Teams building schema-validated filing pipelines, historical retrieval indexes, and RAG corpora over the full EDGAR corpus add this record so queries about discontinued form types do not return gaps.
Practitioners assembling end-to-end SEC histories for fund-rationalization projects, reorganization diligence, or merger documentation need every submission type that ever appeared in a registrant's record. For funds continuously registered since the mid-1990s, a 485BXTF can sit between an earlier 485APOS and a later 485BPOS; omitting it produces a visibly broken timeline. The accession number, filer identifier, and prior-PEA cross-reference are the fields that slot the entry into place.
Researchers in securities regulation and administrative law treat the dataset as a closed, bounded corpus for empirical work on the final months of the election-based 24f-2 regime. Because the form is fully retired, the corpus is exhaustive by construction — useful for case studies of which registrants used the redesignation mechanism and for characterizing the workflow the 1998 rulemaking eliminated.
The use cases below are correspondingly documentary: they support reconstruction of a specific pre-1998 redesignation event, not ongoing monitoring or large-scale analytics.
Fund-complex compliance staff working an audit response or an internal registration-history reconstruction use the record to slot the redesignation event into a registrant's amendment chain across the Rule 24f-2 transition. The relevant fields are entities[0].cik, entities[0].fileNo, accessionNo, and filedAt from metadata.json, paired with the prior-PEA reference, the Rule 485(b)(1)(iii) checkbox, and the new effective date in document-1.txt. The output is a dated entry in the registrant's internal effectiveness ledger pointing at the earlier 485APOSF being redesignated.
Litigation-support analysts handling rescission claims, prospectus-defect allegations, or share-class history questions tied to fund issuances in late 1997 or early 1998 use the filing as a primary-source exhibit. The cover-page file numbers, the dual 1933 Act / 1940 Act post-effective amendment numbers, the incorporation-by-reference paragraph naming the prior 485(a) amendment, and the certified signature block are the evidentiary fields. The dataset's role is to deliver the as-filed text and EDGAR-header metadata that authenticate the exhibit.
Securities-law treatise authors, regulatory historians, and academic researchers writing on Securities Act Release No. 7473 and the January 1998 Rule 24f-2 reform cite the record as a worked example of how the redesignation-plus-24(f)-election mechanism operated in practice. The Rule 24f-2 declaration paragraph, the four-checkbox Rule 485 election panel, and the cross-reference sheet in document-1.txt are the textual anchors. The output is a footnote, exhibit, or appendix in a treatise update, law review article, or expert report.
Data engineers mirroring every submission type that has ever appeared on EDGAR ingest this record so that queries for formType = "485BXTF" resolve to a real accession rather than an empty set. The work touches formType, accessionNo, the documentFormatFiles inventory, and the linkToFilingDetails / linkToHtml / linkToTxt URLs. The output is a validated row in a submission-type registry, a passing test in a historical-coverage suite, or a non-empty shard in a full-EDGAR retrieval index.
Practitioners building end-to-end SEC filing histories for fund-rationalization, reorganization diligence, or merger documentation use the record to bridge a 485APOSF and a later 485BPOS in a single registrant's record. The entities block, accessionNo, filedAt, and the prior-PEA reference inside document-1.txt are the fields that anchor the entry. The output is a chronologically complete timeline exhibit in which the redesignation event is visible rather than silently dropped.
The Form 485BXTF Files dataset is served by the sec-api.io API. Three access methods are available: a metadata index endpoint, a full archive download, and per-container downloads referenced by the index.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-485bxtf-files.json
This endpoint returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, total records and total size, form types, container format, and file types) along with the full archive download URL and the list of container files. Each container entry includes its key, size, record count, last updated timestamp, and direct download URL. Use this endpoint to discover available containers and to monitor which containers were updated in the most recent refresh run, so you can decide which files to pull on a day by day basis. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a9b-96c3-b402fe59d18c",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-485bxtf-files.zip",
4
"name": "Form 485BXTF Files Dataset",
5
"updatedAt": "2026-04-16T09:04:56.443Z",
6
"earliestSampleDate": "1997-08-01",
7
"totalRecords": 1,
8
"totalSize": 3591,
9
"formTypes": ["485BXTF"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-485bxtf-files/1997/1997-08.zip",
15
"key": "1997/1997-08.zip",
16
"size": 3591,
17
"records": 1,
18
"updatedAt": "2026-04-16T09:04:56.443Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-485bxtf-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive covering all Form 485BXTF filings from August 1997 through the form's discontinuation in January 1998. Because the dataset is very small, downloading the entire archive in one request is the simplest option for most users. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-485bxtf-files/1997/1997-08.zip?token=YOUR_API_KEY
Downloads an individual monthly container file instead of the full dataset. Container paths are listed in the dataset index JSON under containers[].downloadUrl. This endpoint requires an API key.
The dataset covers EDGAR submissions filed under the 485BXTF submission type — Rule 485(b)(1)(iii) post-effective amendments that designated a new effective date for a previously filed Rule 485(a) amendment, by registrants that had elected indefinite registration under Section 24(f) of the Investment Company Act of 1940 and former Rule 24f-2. The trailing F flags the Section 24(f) election; the XT segment flags the redesignation-of-effective-date function under Rule 485(b)(1)(iii).
One record represents a single EDGAR 485BXTF submission, stored in an accession-keyed folder containing a metadata.json with EDGAR header- and document-level facts and one document-1.txt containing the as-filed cover page, Rule 24f-2 declaration, Rule 485(b) effective-date checkbox, cross-reference sheet, incorporation-by-reference paragraph, and signature block. Image attachments from the original EDGAR submission are excluded.
Filers are registered investment companies that had affirmatively elected indefinite registration under Section 24(f) and Rule 24f-2 — primarily open-end management investment companies registered on Form N-1A and unit investment trusts registered on Form N-8B-2 (including insurance-company separate accounts issuing variable annuity or variable life contracts). Closed-end funds, business development companies, and operating-company issuers never used Rule 485 and are excluded.
The submission type was active only between August 1997 and January 1998. The Commission's adoption of amendments to Rule 24f-2 in Securities Act Release No. 7473 / Investment Company Act Release No. 22920 made indefinite registration automatic for open-end funds and unit investment trusts, eliminated the Section 24(f) election as a filing-level distinction, and retired the entire F-suffixed Rule 485 branch — including 485APOSF, 485BPOSF, 485A24E, 485B24E, and 485BXTF. The EDGAR record set is therefore the complete record set, and no new records can ever be added.
The earliest sample date is August 1, 1997, and the dataset terminates with the January 1998 retirement of the F-suffixed submission types. Any equivalent effective-date redesignation activity after that date migrated to the surviving non-F Rule 485 family (principally 485BPOS) and is not part of this dataset.
The dataset is distributed as a ZIP archive. Each accession-keyed folder contains a metadata.json (JSON) and one or more document-{N}.txt files (plain ASCII), keyed by the EDGAR document sequence number. There is no XBRL content because Form 485BXTF predates XBRL for fund filings, and the linkToXbrl, dataFiles, and seriesAndClassesContractsInformation fields in metadata.json are permanently empty.
485APOSF carries substantive marked-up registration-statement and prospectus changes by a Section 24(f) elector and triggers the Rule 485(a) staff-review window before automatic effectiveness; 485BPOSF carries immediately effective Rule 485(b)(1) updates such as annual financial updating by the same population. 485BXTF is mechanically a sub-species of Rule 485(b) authorized exclusively by Rule 485(b)(1)(iii): it carries no disclosure payload and does nothing more than redesignate the effective date of a prior 485APOSF amendment in the same registrant's chain.