The Form 485BXT Files Dataset packages every Form 485BXT post-effective amendment filed to EDGAR by registered investment companies from September 1996 to the present. Form 485BXT is a procedural amendment filed under Rule 485(b)(1)(iii) of the Securities Act of 1933 by mutual fund trusts, ETF trusts, and insurance company separate accounts to designate a new effective date for a previously filed Rule 485(a) post-effective amendment — a scheduling tool used when staff comments on the underlying amendment cannot be cleared in time, or when fund complexes need to align effective dates across series, share classes, or related trusts. Each record corresponds to one EDGAR submission under a unique accession number, materialized as an accession folder containing a structured metadata.json describing the EDGAR submission header and a primary .htm document carrying the Form N-1A (or N-2/N-3/N-4/N-6/N-14) facing page wrapped in EDGAR's SGML envelope. The dataset is distributed as a ZIP archive grouped into one monthly container per calendar month, with file types TXT, JSON, HTML, and PDF.
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 Form 485BXT Files Dataset is built from the universe of EDGAR submissions whose form type is 485BXT — the post-effective amendment to a Securities Act registration statement filed pursuant to Rule 485(b)(1)(iii). Form 485BXT is itself administrative in character: it does not republish the prospectus or the statement of additional information, but instead carries a facing page that re-designates the effective date of an earlier Rule 485(a) post-effective amendment, identifies that prior amendment by number and filing date, and is signed by trust officers. The substantive prospectus and SAI content remain housed in the underlying 485(a) amendment to which the 485BXT relates.
The dataset covers all Form 485BXT filings submitted to EDGAR from September 1996 — coinciding with mandatory EDGAR filing for investment companies — to the present. For each accession number the archive includes a metadata file and all documents in the original EDGAR submission except image files; image binaries (entries of type GRAPHIC) are stripped, while their EDGAR URLs remain inside metadata.json for retrieval. Records are grouped chronologically into one ZIP per calendar month under a year directory, producing the path shape <year>/<year>-<month>.zip -> <year>-<month>/<accession>/. The container format is ZIP and the file types found in the dataset are TXT, JSON, HTML, and PDF, accommodating older ASCII submissions and any auxiliary PDF documents alongside the universal metadata.json and the modern .htm primary document.
A single record in the Form 485BXT Files Dataset corresponds to one EDGAR submission of Form 485BXT under a unique accession number. Each record is materialized as one folder named with the 18-digit, zero-padded accession number with the dashes stripped (for example 000182912625004769, which corresponds to EDGAR accession 0001829126-25-004769). Inside that folder are exactly two files: a structured metadata.json describing the EDGAR submission header and document inventory, and a single primary .htm document that carries the Form 485BXT facing-page content wrapped in EDGAR's SGML envelope.
One record therefore equals one filing event, not one fund, not one share class, and not one registration statement. A single 485BXT may, however, designate a new effective date for a post-effective amendment that simultaneously covers many fund series and many share classes belonging to the same registrant trust; the per-record metadata.json enumerates all of those series and class identifiers under the same accession.
Form 485BXT is a post-effective amendment to a registration statement filed by an open-end management investment company (typically a mutual fund trust, ETF trust, or unit investment trust) on Form N-1A, Form N-2, Form N-3, Form N-4, Form N-6, or Form N-14. The form is filed under Rule 485(b)(1)(iii) of the Securities Act of 1933, which permits a registrant that has previously filed a Rule 485(a) post-effective amendment to designate a new, later effective date for that earlier amendment. The mechanism is most often used to give the registrant additional time to negotiate SEC staff comments on the underlying 485(a) filing, to align prospectus effectiveness with a fiscal calendar, to coordinate the launch of new share classes or new series, or to delay an effective date that would otherwise occur automatically under the staggered effectiveness regime of Rule 485(a).
The 485BXT filing itself is administrative in character. It does not republish the prospectus or the statement of additional information; it consists chiefly of the Form N-1A (or N-2/N-3/N-4/N-6/N-14) facing page, the relevant pre-effective and post-effective amendment numbering, the explicit Rule 485(b)(1)(iii) designation of the new effective date, an identification of the prior 485(a) post-effective amendment being delayed, and a signature page. The substantive prospectus and SAI content remain housed in the underlying 485(a) amendment to which the 485BXT relates.
Each record is built from two parallel layers:
metadata.json carrying submission-level identifiers, filer entity information, fund series and class identifiers, the EDGAR document inventory, and canonical public URLs..htm file holding EDGAR's SGML <DOCUMENT> wrapper around the filer-rendered HTML of the Form N-1A (or sibling form) facing page.There is no separate XBRL payload, no financial-data file, and no separate exhibit document. Image binaries that may be referenced from the EDGAR filing-index page (typically logos, signature graphics, or scanned exhibits tagged as GRAPHIC in the document inventory) are intentionally excluded from the archived record; only their URL references remain inside metadata.json. The complete-submission .txt SGML wrapper produced by EDGAR's submission system is likewise not packaged as a separate file inside the record, although its public URL is exposed via linkToTxt.
The folder is the unit of a record. Its name is purely numeric (the 18-digit accession with dashes removed) and serves as the join key both to the dashed accessionNo inside metadata.json and to the linkToFilingDetails URL on sec.gov/Archives/edgar/data/<cik>/<accession-digits>/. There is no nested directory structure beneath the accession folder.
metadata.jsonmetadata.json is a single JSON object that describes the filing at the level EDGAR's submission header records it. The intentional fields are:
formType - the literal string "485BXT".accessionNo - the EDGAR accession number in dashed form (e.g. "0001829126-25-004769").description - the canonical human-readable form label, consistently "Form 485BXT - New effective date for post-effective amendment [Rule 485(b)(1)(iii)]".filedAt - the ISO-8601 acceptance timestamp, including the EDGAR Eastern-time UTC offset (e.g. "2025-06-27T16:44:52-04:00").linkToFilingDetails - URL of the primary 485BXT .htm document on sec.gov.linkToTxt - URL of the full SGML submission wrapper on EDGAR.linkToHtml - URL of the EDGAR filing-index HTML page for the accession.linkToXbrl - empty string for this form, because Form 485BXT carries no XBRL payload.id - a 32-character hexadecimal identifier internal to the dataset.documentFormatFiles[] - an inventory of every document EDGAR registered as part of the original submission. Each element exposes sequence (string; may be " " for the SGML wrapper), size in bytes (string), documentUrl, description, and type. Typical type values are "485BXT" for the primary content document, "GRAPHIC" for image attachments referenced from inside the HTML, and " " for the complete-submission TXT wrapper itself.dataFiles[] - inventory of structured/financial data files; consistently empty ([]) for this form.entities[] - one or more filer entries. The same registrant frequently appears twice in this array, once with act: "40" (Investment Company Act of 1940 registration, file-number prefix 811-) and once with act: "33" (Securities Act of 1933 registration, file-number prefix 333-), because the post-effective amendment is filed against both registration statements simultaneously. Per-entity fields include companyName (suffixed with (Filer)), cik, fileNo, filmNo, irsNo (sometimes all zeros), stateOfIncorporation, act, type ("485BXT"), and optionally fiscalYearEnd (a four-digit MMDD string such as "0331" or "0531").seriesAndClassesContractsInformation[] - the SEC's series-and-class taxonomy for fund offerings. Each element is a { series, name, classesContracts[] } triple where series is the SEC-assigned series identifier (S followed by nine digits), and each entry inside classesContracts[] is a { name, classContract } pair where classContract is the SEC-assigned class/contract identifier (C followed by nine digits). Class entries may additionally carry a ticker. A single 485BXT may enumerate anywhere from one series with one class to many series with multiple classes each, depending on how many funds the underlying registration statement covers..htm documentThe primary document is named by the filing agent (examples include bondbloxxetf_485bxt.htm, d944651d485bxt.htm, tm2517256d7_485bxt.htm, ea0247002-01_485bxt.htm, and the generic f485bxtfacingpage.htm); the only consistent convention is the .htm extension, often with the literal token 485bxt somewhere in the basename. Although the extension is .htm, the file is not pure HTML. It is wrapped in EDGAR's SGML document envelope:
1
<DOCUMENT>
2
<TYPE>485BXT
3
<SEQUENCE>1
4
<FILENAME>...
5
<DESCRIPTION>485BXT
6
<TEXT>
7
<HTML>...filer-rendered facing page...</HTML>
8
</TEXT>
9
</DOCUMENT>
The <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> lines are EDGAR header tags inserted by the submission system; the actual prose lives inside <TEXT> as a self-contained HTML document. Inside that inner HTML, the content is structured as the facing page of a Form N-1A registration statement (or the analogous facing page of N-2, N-3, N-4, N-6, or N-14), and typically presents the following blocks in approximately this order:
<date>".333- series) and the Investment Company Act of 1940 file number (the 811- series), often arranged in a left/right cap structure at the top of the page.FORM N-1A) and the legend "REGISTRATION STATEMENT UNDER THE SECURITIES ACT OF 1933" and/or "REGISTRATION STATEMENT UNDER THE INVESTMENT COMPANY ACT OF 1940".Document length varies materially with the amount of cover-page boilerplate the filer chooses to include. Lean ETF facing pages can be on the order of tens of kilobytes, while filings from large fund complexes that incorporate fuller signature pages, explanatory notes, or extensive series tables can reach several hundred kilobytes. Markup style varies by filing agent: Donnelley/Toppan-style filings rely on dense inline <P STYLE="..."> paragraph formatting, while Workiva/RDG-style filings use <div style="..."> flow blocks with absolute positioning, but both produce semantically equivalent facing-page content.
The record includes, for each accession:
metadata.json, including filer identity (CIK, IRS number, state of incorporation), the dual 33/40 Act file-number registrations and corresponding film numbers, fund series and class identifiers with optional tickers, fiscal year end, the complete EDGAR document inventory, and the canonical public URLs for the filing index, the SGML submission, and the primary document..htm document with its EDGAR SGML wrapper intact, preserving both the EDGAR-injected <DOCUMENT> metadata lines and the filer's full inner HTML facing page.GRAPHIC listed in documentFormatFiles[]) are stripped from the archived record. Their EDGAR URLs remain inside metadata.json for retrieval, but the bytes themselves are not packaged..txt SGML submission envelope wrapper produced by EDGAR (typically the entry whose type is " " in documentFormatFiles[]) is not carried as a separate file inside the record; only its URL is exposed via linkToTxt.linkToXbrl is empty and dataFiles[] is empty); risk/return summary XBRL, where it exists for a fund, is associated with the substantive prospectus filings, not with the administrative 485BXT designation.The substantive content required on a Form 485BXT facing page has been remarkably stable since Rule 485 was adopted in its modern form. The amendment-numbering convention, the dual 33/40 Act file-number presentation, the Rule 485(b)(1)(iii) designation paragraph, and the signature block have all persisted across the dataset's full coverage from the mid-1990s to the present. The most material structural change at the registrant-information layer was the introduction of SEC series and class identifiers (the S and C IDs) in 2006 under the EDGAR series-and-class reporting regime; for filings on or after that adoption, the seriesAndClassesContractsInformation[] block in metadata.json becomes populated, whereas earlier filings carry only registrant-level identifiers. Tickers within class entries became progressively more complete as filers populated the EDGAR class-ticker field. The form's amendment-numbering practice — separately tracking 1933 Act post-effective amendment numbers and 1940 Act amendment numbers on the same facing page — has not changed.
EDGAR began accepting electronic Form 485BXT filings in the mid-1990s as plain ASCII text inside the SGML submission envelope, and through the late 1990s and into the early 2000s the primary document was typically delivered as a .txt body. Beginning in the early 2000s, filing agents shifted Form 485BXT primary documents to inline HTML wrapped in the same SGML <DOCUMENT> envelope, which is the convention that has dominated the dataset for the last two decades. Modern filings are almost exclusively .htm documents. The file-types found in the dataset are TXT, HTML, PDF, and JSON, accommodating older ASCII submissions and any auxiliary PDF documents that may appear in particular filings, alongside the universal metadata.json.
Throughout these format transitions the EDGAR SGML wrapper (the outer <DOCUMENT>/<TYPE>/<SEQUENCE>/<FILENAME>/<DESCRIPTION>/<TEXT> block) has remained the canonical container around the primary document body, so a parser that strips the SGML envelope first and then dispatches on the inner content type works uniformly across the time range. Form 485BXT carries no XBRL, so no inline XBRL transition is relevant to this record type.
accessionNo inside metadata.json are the same identifier in two notations; either can be used to join records across systems.entities[] because the same trust is registered both under the Securities Act of 1933 (act "33", file-number prefix 333-) and under the Investment Company Act of 1940 (act "40", file-number prefix 811-). These are not duplicate filers; they are two distinct registration statements being amended simultaneously, each with its own fileNo and filmNo.seriesAndClassesContractsInformation[] array is the authoritative enumeration of which fund offerings the 485BXT covers. A single accession can span many series and many classes; treating one record as one fund will misrepresent multi-series amendments. Conversely, the absence of this block on older filings does not mean the filing covered no series — it means series/class IDs predated the EDGAR taxonomy.metadata.json; the cross-reference must be parsed from the prose or matched on registrant CIK and amendment numbering..htm extension on the primary document is misleading for naive HTML parsers: the file begins with EDGAR SGML header lines (<DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, <TEXT>) before the inner <HTML> element starts, and ends with the matching </TEXT></DOCUMENT> after </HTML>. Robust extraction should isolate the inner <TEXT>...</TEXT> region before applying HTML parsing.sec.gov rather than to local files inside the accession folder, because graphic binaries are deliberately excluded from the archive. Resolving those references requires fetching from EDGAR.Each Form 485BXT is filed by a registered investment company — the registrant on whose registration statement the underlying amendment was filed — for the sole purpose of designating a new effective date for a previously filed Rule 485(a) post-effective amendment. The filer is the trust, corporation, or separate account that holds the registration statement, acting through its officers and counsel. The filing is procedural: it does not introduce new prospectus disclosure, it controls when an earlier 485APOS becomes effective. Each 485BXT is therefore tied to a specific prior 485APOS and typically references that filing's accession number, file number, and proposed amendments.
Form 485APOS filers are limited to investment companies eligible to use the Rule 485 regime under the Securities Act of 1933 and the Investment Company Act of 1940:
The legal filer is always the registrant. Investment advisers, sub-advisers, principal underwriters, insurance depositors, and individual portfolios discussed in the amendment are not filers of record, even when the delayed disclosure concerns them directly.
Closed-end funds, business development companies, and operating-company issuers do not use Rule 485 and do not produce 485BXT records. Closed-end interval funds with continuous offerings file under Rule 486 instead.
Form 485BXT is filed under Rule 485(b)(1)(iii) of the Securities Act, which lets a registrant designate a new effective date for a previously filed 485APOS. A 485APOS otherwise becomes effective automatically 60 days after filing (or 75 days for amendments adding a new series). The 485BXT delays or relocates that automatic date.
The form is purely event-driven, with no periodic or calendar cadence. It arises only when a registrant has an outstanding 485APOS whose default effective date it wishes to move. Common triggers:
Timing constraints:
Filing volume across a fund complex tends to cluster around annual prospectus update cycles tied to fiscal year-end and the Section 10(a)(3) 120-day update obligation.
Form 485BXT serves a narrow procedural function under Rule 485(b)(1)(iii): redesignating the effective date of a previously filed post-effective amendment. It shares filer population with the rest of the 485-series and the underlying N-series registration statements, but its role is timing, not disclosure. The most useful comparisons are to the other 485 variants, the N-series originals they amend, and the Rule 497 definitive-materials family that follows effectiveness.
485APOS is the substantive amendment that 485BXT exists to defer. It carries material prospectus or SAI changes — new strategies, fee changes, fund mergers, new share classes — and triggers an automatic 60-day (or longer) delayed effectiveness window for staff review.
485BXT carries no disclosure content. It is paired with a specific prior 485APOS (typically referencing its accession number) and only shifts when that amendment becomes effective. Use 485APOS for what changed; use 485BXT for when it takes effect.
485BPOS is the standard annual update vehicle, effective immediately or on a near-term designated date because it contains only non-material changes (annual financials, conformity edits, or revisions previously cleared by staff). It carries the full updated prospectus and SAI.
The contrast with 485BXT is twofold: 485BPOS contains the substantive document and is filed under Rule 485(b)(1)(i)–(ii); 485BXT contains no document and is filed solely under Rule 485(b)(1)(iii) to reset an effective date. Funds pushing out a routine annual update file 485BPOS; funds delaying a pending substantive amendment file 485BXT.
These are the legacy Rule 24e-2 counterparts used to register additional shares for open-end funds before modernization of registration mechanics. They share the post-effective amendment lineage but operate under a different statute (Investment Company Act share-count registration, not Securities Act effective-date timing). They appear infrequently today and rarely overlap with 485BXT use cases.
These are the foundational registration forms every 485-series filing amends — N-1A for open-end funds and most ETFs, N-2 for closed-end funds, N-3/N-4/N-6 for variable insurance separate accounts. They contain the complete prospectus, SAI, and Part C exhibits.
A 485BXT presupposes one of these as its base registration; it cannot exist without an effective N-series filing and a pending 485APOS to defer. To reconstruct current prospectus content, researchers need the N-series original plus the most recent effective 485BPOS or 485APOS. 485BXT alone reveals timing, never substance.
Form 497 and its variants (497K summary prospectus, 497J certification) deliver the final investor-facing prospectus and sticker supplements after a registration or amendment becomes effective.
497 and 485BXT sit on opposite sides of effectiveness. 485BXT is pre-effectiveness scheduling; 497 is post-effectiveness delivery. A fund that defers a 485APOS via 485BXT will, once effective, follow up with 497 filings carrying the definitive text. The two are sequential, not substitutable.
A fund could withdraw a pending 485APOS and submit a fresh one, but that restarts the 60-day staff review clock and discards review progress already made. 485BXT preserves the existing 485APOS and ongoing staff dialogue while sliding the effective date forward — to accommodate unresolved comments, align with a fiscal-year boundary, coordinate with related fund launches, or sync with distribution timelines. It is the lightweight scheduling tool inside an otherwise heavy-review process.
The Form 485BXT Files Dataset is distinct because it isolates a single procedurally narrow filing whose function is calendar management, not disclosure. It is event-driven rather than periodic, and always paired with a 485APOS that carries the actual content. It does not substitute for 485APOS or 485BPOS in reconstructing prospectus changes, for the N-series in establishing fund structure, or for Form 497 in capturing definitive investor materials. Its analytical value lies in tracing the timing and friction of fund registration amendments — staff-comment cycles, deferred effectiveness, and the choreography of mutual fund disclosure updates — not in the disclosures themselves.
The Form 485BXT Files Dataset is consumed by specialists in fund registration mechanics who care about a small set of fields: the prior 485(a) accession reference, the new effective date, registrant CIK and series/class identifiers, and the gap between original and revised effectiveness.
In-house and outside attorneys specializing in the Investment Company Act use the dataset as a precedent library when drafting their own 485BXT filings. They study cover-page conventions for citing the prior 485(a) amendment, accepted phrasing for new effective dates, and how peer registrants sequence multiple redesignations on a single registration statement. The cover page text and EDGAR header metadata are the load-bearing fields.
CCOs and registration compliance staff at fund complexes track their own 485BXT history to measure how often prospectus updates slip past the originally designated effective date. The spread between the 485(a) date, the original effective date, and the new effective date set in 485BXT exposes weaknesses in internal drafting calendars and disclosure controls.
Filing agents and registration operations staff at third-party fund administrators prepare and transmit 485BXT filings on behalf of multiple fund clients under tight, comment-cycle-driven deadlines. They use the dataset to validate template accuracy, confirm header tag values, check date formatting against accepted EDGAR conventions, and reconcile internal filing calendars with what EDGAR actually accepted.
Product managers launching new share classes, repricing fees, or reorganizing fund lineups use the dataset to set realistic launch timelines. Each 485BXT signals a delayed product change, so the filing date versus new effective date and the frequency of redesignations per registrant inform internal schedules and expectations communicated to distribution, marketing, and the board.
Examination, enforcement, and policy analysts use the dataset to study aggregate use of Rule 485(b)(1)(iii): frequency per registrant, repeated redesignations on the same 485(a), length of delay, and clustering around comment cycles. This supports examination scoping and rule-review work on Rule 485 mechanics.
Vendors maintaining fund reference databases and prospectus-status feeds parse 485BXT filings to refresh "prospectus effective as of" fields and linkage records between amendments. The metadata file, the new effective date, and the prior 485(a) accession reference drive downstream updates and subscriber notifications keyed to CIK and series.
Strategy teams at asset managers and consulting firms aggregate 485BXT filings by registrant, year, and underlying amendment type to estimate how much staff-comment friction peer complexes encounter and which product categories (index, alternatives, new asset classes) face the longest reviews. They typically join CIK, registrant name, filing date, and prior 485(a) reference to N-1A and 485APOS data.
Finance, accounting, and law researchers treat 485BXT as a clean proxy for comment-driven delay, since its sole purpose is to redesignate an effective date. They construct review-duration measures, test which fund characteristics correlate with longer reviews, and track shifts across regulatory regimes using the dataset's near-three-decade span back to September 1996.
Across all these users the load-bearing fields are the same: registrant CIK and name, filing date, prior 485(a) accession reference, and the new designated effective date. Lawyers and compliance officers draft and supervise the filings, operations teams transmit them, product and analytics teams read them as friction signals, regulators and academics study the review process in aggregate, and data vendors keep downstream effective-date records aligned.
The Form 485BXT Files Dataset supports a small set of operational and analytical workflows centered on fund registration timing. The use cases below tie directly to fields in metadata.json (filer CIK, series/class IDs, filedAt, prior 485(a) reference) and to the Rule 485(b)(1)(iii) designation paragraph inside the primary .htm facing page.
Building a fund-registration delay panel. Researchers and compliance analysts join accessionNo, filedAt, registrant CIK from entities[], and the prior 485(a) amendment number and filing date parsed from the inner HTML to compute the gap between originally designated and redesignated effective dates. The resulting panel is used to measure staff-comment friction per registrant and per fund family across the dataset's coverage from the mid-1990s onward.
Maintaining "prospectus effective as of" reference data. Reference-data vendors parse the new effective date from the Rule 485(b)(1)(iii) paragraph and use seriesAndClassesContractsInformation[] to fan that date out to every affected series ID (S followed by nine digits) and class ID (C followed by nine digits, with optional ticker). This refreshes downstream subscriber feeds keyed to CIK and series without waiting for the eventual 485BPOS.
Drafting precedent library for 485BXT filings. Outside fund counsel and filing agents query the dataset by registrant peer group to retrieve the inner <TEXT> HTML of facing pages, extracting accepted phrasing for the new-effective-date designation, the dual 333-/811- file-number cap structure, and the post-effective amendment numbering convention. They reuse these patterns when preparing their own 485BXT cover pages and signature blocks.
Monitoring repeated redesignations on the same 485(a). Examination staff and CCOs cluster filings by registrant CIK plus referenced prior 485(a) accession to detect cases where the same underlying amendment is delayed two or more times. The count of redesignations and total elapsed delay flags amendments with unusual staff-comment cycles for examination scoping or internal disclosure-controls review.
Reconciling EDGAR-accepted submissions against internal filing calendars. Filing operations teams at fund administrators diff the filedAt timestamp, formType, dual act: "33" / act: "40" entity entries, and documentFormatFiles[] inventory in metadata.json against their internal ticketing system to confirm each transmitted 485BXT was accepted with the correct amendment numbers and series coverage.
Estimating product-launch timing for new share classes. Product managers filter records where seriesAndClassesContractsInformation[] contains newly assigned class IDs or tickers and compute the distribution of delay between original and redesignated effective dates. The output calibrates realistic launch windows communicated to distribution, marketing, and the board for analogous future share-class rollouts.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-485bxt-files.json
This endpoint returns dataset metadata including the name, description, last updated timestamp, earliest sample date (1996-09-01), total records and total size, covered form types (485BXT), container format (ZIP), and file types (TXT, JSON, HTML, PDF). It also returns the full dataset download URL and the list of monthly container files, each with its key, size, record count, updated timestamp, and download URL. Use this endpoint to monitor which containers were updated in the latest refresh run and decide on a daily basis which containers to download. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-690a-95a0-53fd3a111f24",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-485bxt-files.zip",
4
"name": "Form 485BXT Files Dataset",
5
"updatedAt": "2026-04-28T02:58:03.574Z",
6
"earliestSampleDate": "1996-09-01",
7
"totalRecords": 37940,
8
"totalSize": 264806586,
9
"formTypes": ["485BXT"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON", "HTML", "PDF"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-485bxt-files/2026/2026-04.zip",
15
"key": "2026/2026-04.zip",
16
"size": 13818783,
17
"records": 154,
18
"updatedAt": "2026-04-28T02:58:03.574Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-485bxt-files.zip?token=YOUR_API_KEY
Downloads the complete Form 485BXT Files Dataset as a single ZIP archive containing all monthly containers from September 1996 to present. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-485bxt-files/2026/2026-04.zip?token=YOUR_API_KEY
Downloads one monthly container ZIP, allowing you to retrieve only the filings for a specific month rather than the full dataset. This endpoint requires an API key.
The dataset covers Form 485BXT, a post-effective amendment to a registered investment company's registration statement filed pursuant to Rule 485(b)(1)(iii) of the Securities Act of 1933. Its sole purpose is to designate a new effective date for a previously filed Rule 485(a) post-effective amendment.
One record corresponds to a single EDGAR submission of Form 485BXT under a unique accession number, materialized as one folder named with the 18-digit zero-padded accession number with dashes stripped. Each folder contains a metadata.json describing the EDGAR submission header and a primary .htm document carrying the Form N-1A (or sibling N-form) facing page wrapped in EDGAR's SGML envelope.
Filers are registered investment companies eligible to use the Rule 485 regime: open-end mutual funds and ETFs registered on Form N-1A, and insurance company separate accounts registered on Form N-3, N-4, or N-6. Closed-end funds, business development companies, and operating-company issuers do not use Rule 485 and do not appear in the dataset.
Form 485BXT is purely event-driven; it is filed after a 485APOS but before that amendment's automatic effective date (typically 60 days after filing, or 75 days for amendments adding a new series). Common triggers include unresolved SEC staff comments, coordination across a fund complex, prospectus printing logistics, and pending board or sub-adviser actions.
485APOS is the substantive amendment carrying material prospectus or SAI changes; 485BPOS is the immediately effective amendment used for routine annual updates. 485BXT carries no disclosure content and is filed solely under Rule 485(b)(1)(iii) to reset the effective date of a prior 485APOS, so it should be used to study timing and friction in the registration cycle, not to reconstruct prospectus changes.
The dataset covers all Form 485BXT filings submitted to EDGAR from September 1996 to the present, with September 1996 coinciding with mandatory EDGAR filing for investment companies. It is distributed as ZIP containers grouped one per calendar month under a year directory, and the file types found inside are TXT, JSON, HTML, and PDF.
No. Image binaries (entries of type GRAPHIC in documentFormatFiles[]) are stripped from the archive, though their EDGAR URLs remain inside metadata.json. The underlying Rule 485(a) post-effective amendment that the 485BXT delays is a separate EDGAR filing under a different accession and is not bundled into this record; the 485BXT references that prior amendment only by amendment number and filing date.