The Form F-10EF Files Dataset is a structured collection of auto-effective Securities Act registration statements filed on EDGAR by Canadian issuers eligible to use the U.S.-Canada Multijurisdictional Disclosure System (MJDS). Each record represents a single F-10EF accession — the registration statement plus its full set of issuer-supplied exhibits — packaged as an accession-numbered folder inside a monthly ZIP container alongside a metadata.json summary that mirrors the EDGAR submission header. Filings come directly from MJDS-eligible Canadian issuers acting as foreign private issuers, with co-registrant guarantor subsidiaries appearing where guaranteed debt is registered. The dataset covers F-10EF accessions from May 2007 through the present and is distributed as monthly ZIP containers built from HTML, JSON, and TXT artifacts.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset packages every F-10EF accession received by EDGAR — the auto-effective variant of the MJDS registration statement under Securities Act Rule 467(b). Form F-10 is one of the four MJDS forms that allow large, seasoned Canadian issuers to register securities for sale into the United States by adapting a Canadian-prepared prospectus to U.S. disclosure requirements rather than producing a separate U.S.-style registration statement. The "EF" suffix indicates that the filing is declared effective immediately upon filing, with no SEC staff review or waiting period, when the registrant has met specified reporting-history and float thresholds and the offering meets the conditions of Rule 467(b).
Substantively, an F-10EF combines:
The dataset is distributed as ZIP containers, one per calendar month, beginning with filings from May 2007. Each container expands into a flat directory whose immediate children are accession folders that bundle HTML registration documents, HTML exhibits, an Inline XBRL filing-fee exhibit (when required), and a JSON metadata index.
One record in the Form F-10EF Files Dataset corresponds to a single SEC accession — one Form F-10EF submission filed on EDGAR by a Canadian issuer eligible to use the Multijurisdictional Disclosure System (MJDS). Each record is delivered as an accession-numbered folder inside a monthly ZIP container and bundles every issuer-supplied document of the original EDGAR submission (the registration statement plus its attached exhibits) together with a metadata.json summary that mirrors the EDGAR submission header. The folder name is the SEC accession number with the dashes stripped (e.g., accession 0001104659-25-114606 becomes folder 000110465925114606), giving a stable, deterministic key that joins back to EDGAR.
Each monthly ZIP expands into a flat directory whose immediate children are accession folders; the accession folder is the record. The intra-folder layout is:
1
<accession-no-dashes>/
2
metadata.json (always present, structured index)
3
<preparer>_f10ef.htm (the F-10EF registration statement)
4
<preparer>_ex<n-n>.htm (one HTML file per exhibit)
5
<preparer>_ex-filingfees.htm (Inline XBRL filing-fee exhibit, when required)
6
... (additional exhibit HTMLs as filed)
Document filenames are issuer- and preparer-controlled (Toppan, RR Donnelley, Workiva, and similar stems are common) and are not predictable from the form type alone. The reliable way to identify a document's role is the EDGAR type field, which appears both inside the SGML wrapper of each file and in the documentFormatFiles[] array of metadata.json.
metadata.json indexEvery record carries a metadata.json at the root of the accession folder. It is a single JSON object that mirrors the EDGAR submission header and inventories every document associated with the filing. Its top-level fields are:
formType — always F-10EF for this dataset.accessionNo — canonical accession number with dashes (e.g., 0001104659-25-114606).filedAt — ISO-8601 filing timestamp with timezone (Eastern time on the EDGAR server).description — human-readable form description ("Form F-10EF - Registration Statement for Securities of certain Canadian Issuers, immediately effective.").linkToFilingDetails — direct EDGAR URL to the primary registration document.linkToHtml — URL to the EDGAR filing-index landing page (...-index.htm).linkToTxt — URL to the canonical EDGAR full-submission .txt (the SGML concatenation of all documents).linkToXbrl — URL to a top-level XBRL viewer; commonly empty for F-10EF because structured data lives inside the filing-fee exhibit rather than the registration body.id — stable internal hash identifier for the record.documentFormatFiles[] — inventory of every submission document plus a trailing entry for the complete-submission text file. Each element carries sequence (EDGAR sequence number), size in bytes, documentUrl (sometimes routed via /ix?doc= for inline-XBRL exhibits), description (issuer-supplied, e.g., F-10EF, EXHIBIT 5.1, EX-FILING FEES, GRAPHIC, Complete submission text file), and type (EDGAR document type, e.g., F-10EF, EX-5.1, EX-FILING FEES, GRAPHIC).dataFiles[] — inventory of structured-data files associated with the submission. For F-10EF the typical entry is the extracted XBRL instance document for the filing-fee exhibit (description = "EXTRACTED XBRL INSTANCE DOCUMENT", type = "XML").entities[] — one block per filer or co-registrant carried in the EDGAR header. Fields include companyName with a parenthetical role suffix (e.g., "... Inc. (Filer)", "... Inc. (Co-Registrant)"), cik, fileNo (the SEC 333-... registration file number), filmNo, irsNo, fiscalYearEnd as MMDD, stateOfIncorporation using EDGAR's province/country codes (Canadian provinces appear as A0–A9, e.g., A6 for Ontario), act (33 for the Securities Act), type (the form type for that entity), sic (Standard Industrial Classification code with description), and tickers as an array.seriesAndClassesContractsInformation[] — present for schema consistency but typically empty for F-10EF, which is not an investment-company form.The documentFormatFiles[] array is the authoritative inventory; on-disk siblings reconcile to it by matching the basename of documentUrl to the file on disk, or by matching the <FILENAME> tag inside each document's SGML wrapper.
Every .htm in the container is wrapped in EDGAR's SGML <DOCUMENT> envelope — the same envelope EDGAR uses inside the full-submission .txt. The first lines of every document are SGML headers and the last line is </DOCUMENT>:
1
<DOCUMENT>
2
<TYPE>F-10EF
3
<SEQUENCE>1
4
<FILENAME>tm2517339-2_f10ef.htm
5
<DESCRIPTION>F-10EF
6
<TEXT>
7
<html>... (full HTML body) ...</html>
8
</TEXT>
9
</DOCUMENT>
The <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> tags inside this wrapper duplicate the corresponding fields in documentFormatFiles[], providing two equivalent locator paths. Any HTML parser consuming these documents must skip or strip the leading <DOCUMENT>...<TEXT> and trailing </TEXT></DOCUMENT> lines before parsing the inner markup; otherwise the SGML pseudo-tags will leak into the DOM.
The primary document — type F-10EF, sequence 1, filename pattern <preparer>_f10ef.htm — is the registration statement itself. It is full XHTML with rich inline styling and is typically several hundred kilobytes. Its internal structure follows Form F-10's instruction set adapted for the auto-effective procedure:
Exhibits are stored as separate .htm files in the same accession folder, each wrapped in its own SGML <DOCUMENT> envelope. The exhibit families that appear across the dataset, identified by their EDGAR type and description, include:
EX-1.1) — the underwriting agreement, agency agreement, or equity distribution / at-the-market agreement signed in connection with the take-down.EX-4.x) — for debt offerings, the indenture governing the notes, supplemental indenture, or form of note.EX-4.x) — securities-instrument exhibits when warrants, units, or subscription receipts are part of the offering.EX-5.x) — a signed opinion as to the validity of the securities being registered under the laws of the issuer's province of incorporation, frequently issued by a major Canadian firm.EX-8.x) — opinions on Canadian and/or U.S. federal income tax consequences when material to the offering.EX-23.x) — written consents from the issuer's auditing firm (and any predecessor auditor or auditor of an acquired business whose financial statements are incorporated) to the use of their reports in the registration statement. Plain HTML, frequently a single page, with a signature block for the firm.EX-23.x) — consents from reserves engineers, mining qualified persons, or other technical experts whose reports are incorporated by reference; common for resource issuers using F-10EF.EX-24.1) — authorizing one or more officers to sign amendments and related filings on behalf of named directors.EX-25.x, Form T-1) — for debt offerings, the trustee's statement of eligibility under the Trust Indenture Act.EX-FILING FEES) — the Rule 457 fee table, delivered as an Inline XBRL XHTML document (see below).The numbering scheme follows the Form F-10 instruction set; the dataset's authoritative classifier is the type field, not the issuer-supplied numeric exhibit label, since labels can drift across filers and over time.
The EX-FILING FEES document is structurally distinct from the other exhibits. It is an XHTML file that is simultaneously a valid web document and a machine-readable XBRL instance: it declares the SEC's Filing Fees Data taxonomy and the DEI taxonomy in its namespaces (typically xmlns:ffd="http://xbrl.sec.gov/ffd/<year>" and xmlns:dei="http://xbrl.sec.gov/dei/<year>") and emits both visible and hidden ix:nonNumeric and ix:nonFraction facts. Per-offering-line xbrli:context blocks (offrl_1, offrl_2, ...) scope the line-level facts. Tagged concepts include filing identifiers (ffd:FormTp, ffd:SubmissnTp), entity identifiers (dei:EntityCentralIndexKey, dei:EntityRegistrantName), and the substantive fee mechanics (ffd:FeeRate, security type, amount registered, proposed maximum aggregate offering price, fee calculation, rule references, and offset amounts where the issuer is carrying forward fees from a prior registration). Downstream extraction of fee-table data should rely on the ffd:-namespaced facts in this Inline XBRL document rather than scraping the rendered HTML table.
Each accession folder contains the complete set of issuer-supplied submission documents that EDGAR received, except for the categories noted below. Concretely:
metadata.json, always present.type/description tags.Three categories of EDGAR-attached content are intentionally not bundled into the accession folder:
GRAPHIC). Issuer logos, signature graphics, and other binary attachments referenced by <IMG SRC=...> inside HTML exhibits are excluded. Their inventory entries remain in metadata.json (with documentUrl pointing to EDGAR), and HTML exhibits will contain dangling image references. Consumers who need those graphics must fetch them from EDGAR directly.<accession>.txt). EDGAR's canonical SGML concatenation of every document in the submission is referenced by linkToTxt and listed as the trailing entry of documentFormatFiles[] (with a blank-space sequence and type), but the file itself is not redistributed on disk; the same content is reconstructable from the SGML-wrapped per-document HTMLs that are bundled.dataFiles[] with a documentUrl to EDGAR but is not redistributed in the container, since the Inline XBRL HTML already carries the same facts inline.Form F-10/F-10EF has been a stable MJDS form since 1991, and the broad section ordering of the registration statement (cover, MJDS statements, prospectus or incorporation thereof, Part II undertakings and indemnification, exhibit index, signatures) has not changed substantively across the dataset's coverage window. The notable evolutionary changes affect exhibits and electronic format:
EX-FILING FEES Inline XBRL document. Earlier filings present the fee table only as a calculation-of-registration-fee table on the registration statement cover, with no separate Exhibit 107 and no inline-XBRL fee facts; the dataFiles[] array in those records will not contain an extracted filing-fee XBRL instance.EX-23.x documents and are identified individually in documentFormatFiles[].entities[] array in modern records frequently contains multiple (Co-Registrant) blocks alongside the primary (Filer) block, each with its own CIK, file number, jurisdiction, and SIC. Older equity-only filings more often have a single (Filer) entity.documentFormatFiles[].documentUrl (basename) or via the <FILENAME> SGML header, not via filename heuristics, because preparer-controlled stems vary across issuers.sequence and blank type describes the (excluded) complete-submission .txt and should be treated specially when iterating documents.<IMG SRC> references because graphics are excluded; downstream rendering will show broken images unless graphics are resolved against EDGAR.ffd:-namespaced Inline XBRL facts in the EX-FILING FEES exhibit (or the linked extracted XBRL instance XML on EDGAR) over scraping the rendered HTML, because the XBRL facts are normalized and unambiguously typed.stateOfIncorporation uses EDGAR's province/country code system (Canadian provinces appear as A0–A9); consumers expecting ISO codes must translate.fileNo (333-...) carried in entities[].fileNo.The "EF" suffix designates the filing for immediate effectiveness under Securities Act Rule 467(b), distinguishing it from a standard Form F-10, which is held pending SEC staff review and declared effective by order under Rule 467(a).
The filer is the Canadian issuer itself, acting as a foreign private issuer registrant. To use Form F-10 or F-10EF, the issuer must satisfy the eligibility conditions of the U.S.-Canada Multijurisdictional Disclosure System:
Co-registrant guarantor subsidiaries may sign alongside the principal Canadian issuer where guaranteed debt is being registered. Underwriters, selling security holders, auditors, and counsel appear in the filing but do not file in their own capacity.
Form F-10EF is event-driven, not periodic. A record arises whenever an MJDS-eligible Canadian issuer elects to register a U.S. offering on the auto-effective track. Common triggers include:
Effectiveness occurs at the moment of filing or at a designated time on the filing date specified by the registrant under Rule 467(b). Shelf take-downs after effectiveness are made through prospectus supplements filed under Rule 424(b), corresponding to Canadian supplemented prospectuses. Unused capacity is removed through Form RW or deregistration filings.
EDGAR-based F-10EF records in this dataset begin in May 2007 and continue through the present.
Form F-10EF sits within a tight cluster of MJDS forms for Canadian issuers and the broader registration-statement family used by foreign private issuers and U.S. domestic registrants. Confusion most often arises with adjacent MJDS forms, with non-MJDS shelf registrations, and with the prospectus supplements and free-writing prospectuses that follow an effective F-10 shelf.
Form F-10 (standard MJDS registration statement). The direct sibling. Same MJDS regime, same eligible issuer population, and substantially identical prospectus content. The sole meaningful difference is procedural: a standard F-10 is filed for SEC staff review and effective only upon declaration, while F-10EF is auto-effective on filing. Treat F-10 and F-10EF as complementary halves of the same MJDS shelf universe.
Form F-7 (MJDS rights offerings). MJDS registration narrowly scoped to rights offerings extended by Canadian issuers to existing security holders. Disclosure focuses on rights mechanics rather than a general base prospectus; F-7 cannot serve as a primary capital-raising shelf.
Form F-8 (MJDS business combinations and exchange offers). MJDS registration triggered by a transaction (merger, acquisition, exchange) rather than a capital raise. Disclosure is deal-centric, including target information and exchange terms. Not a shelf vehicle.
Form F-80 (MJDS business combinations, larger issuers). Same purpose as F-8 but calibrated to larger Canadian issuers under different MJDS eligibility thresholds. Useful only for mapping the full MJDS grid (F-10/F-10EF for offerings, F-7 for rights, F-8/F-80 for combinations, 40-F for periodic reporting); not a substitute for F-10EF.
Form F-3 (foreign private issuer shelf, non-MJDS). The non-MJDS short-form shelf for seasoned FPIs, including non-Canadian filers. Built on U.S. integrated disclosure incorporating Form 20-F or 40-F by reference, rather than Canadian prospectus documents. Subject to staff review unless filed as an automatic shelf by a WKSI. Use F-3 for FPI shelf activity outside MJDS; F-10EF when the filer is a Canadian MJDS-eligible issuer relying on home-country disclosure.
Form S-3 (U.S. domestic shelf). The U.S. domestic short-form shelf, built on U.S. GAAP and Regulation S-K. No filer-population overlap with F-10EF; relevant only when mapping equivalent shelf vehicles across issuer regimes.
Form F-1 (foreign private issuer long-form registration). Long-form registration for FPIs that do not qualify for short-form or MJDS treatment, typically IPOs or issuers lacking reporting history. Always staff-reviewed, never auto-effective, and far more disclosure-intensive. Canadian issuers below MJDS thresholds default here.
Form 40-F (MJDS annual report). The reporting-side MJDS counterpart. 40-F is a periodic annual report (AIF, MD&A, audited financials) filed in lieu of 20-F or Form 10-K; it does not authorize securities sales. F-10EF filings routinely incorporate 40-F content by reference, making 40-F a strong complement, not a substitute.
Form 6-K (FPI current and interim reports). Event-driven and interim reporting for FPIs, including MJDS issuers. Triggered by what the issuer makes public in its home jurisdiction rather than by a fixed U.S. event list. Reporting, not registration; useful for tracking ongoing disclosure between F-10EF shelf filings.
Form 424B prospectus supplements. The take-down layer of the shelf process. The F-10EF base prospectus describes the universe of securities that may be offered; 424B supplements (424B2, 424B3, 424B5, etc.) describe each priced tranche actually sold, including final pricing, distribution terms, and use of proceeds. F-10EF alone shows shelf capacity; 424B is required to measure realized issuance, pricing, and syndicates.
Form FWP (free writing prospectus). Supplemental written marketing materials (term sheets, investor presentations, pricing supplements) tied to a take-down off an F-10EF or F-3/S-3 shelf. Not a registration statement and contains no full prospectus disclosure; captures marketing-stage materials around specific tranches.
F-10EF is uniquely defined by three combined attributes: MJDS-only and restricted to qualifying Canadian issuers, a registration statement rather than a periodic or current report, and auto-effective on filing rather than staff-reviewed. Among MJDS forms, F-7, F-8, and F-80 occupy distinct transactional niches and 40-F handles periodic reporting. Among shelf registrations, F-3 and S-3 cover non-MJDS FPIs and U.S. domestic issuers. F-1 covers long-form FPI registration. Downstream, 424B records take-downs and FWP captures marketing materials; 6-K covers interim disclosure. F-10EF is best understood as the auto-effective Canadian shelf base, with 40-F and 6-K as the reporting layer and 424B and FWP as the offering-execution layer.
F-10EF filings are the auto-effective MJDS registration statements through which eligible Canadian issuers reach U.S. investors. Each accession bundles a prospectus, EX-1.1 underwriting agreement, EX-5 validity and EX-8 tax opinions, EX-23 consents, an Inline XBRL EX-FILING FEES exhibit, and EDGAR metadata. A narrow set of cross-border specialists uses these components for distinct purposes.
Capital markets bankers at U.S. and Canadian investment banks use the corpus as a precedent library when structuring bought deals, base shelf takedowns, and cross-border follow-ons. They mine the prospectus for pricing mechanics, greenshoe size, gross spreads, and stabilization language, and read EX-1.1 for commission grids, market-out and termination triggers, and indemnification carve-outs when negotiating engagement letters.
U.S. and Canadian counsel benchmark prospectus drafting against current peer practice. They examine MJDS eligibility statements, incorporation-by-reference of Canadian base shelf prospectuses and AIFs, enforceability-of-judgments risk factors, and Canadian-to-U.S. accommodations in financial statement presentation. EX-5 validity and EX-8 tax opinions serve as drafting templates; NI 44-101/44-102 references and passport-system disclosures are tracked across registrants.
Underwriters' counsel treat EX-1.1 and ancillary exhibits as their working precedent: representation-and-warranty packages, conditions precedent, comfort-letter and 10b-5 negative-assurance hooks, MAC outs, indemnity and contribution language, and bring-down opinion mechanics. They also compare FINRA compensation-review handling and DRS or book-entry settlement provisions across deals.
Audit engagement partners and accounting-firm capital markets groups use EX-23 consents and incorporated financials to verify how their firm and peers consent in MJDS filings, including PCAOB-versus-Canadian-standards references and dual-standards reporting. Pro forma and significant-subsidiary disclosures inform comfort-letter scoping for takedowns.
Equity analysts covering cross-listed names model dilution from secondary issuances and convertibles using the prospectus and offering terms. Credit desks read indenture exhibits, covenant summaries, and ranking disclosures when sizing new-issue allocations. Event-driven funds scan filings for capital-raise signals, MAC language, and selling-shareholder participation that drive trading around takedowns.
Credit analysts at rating agencies update issuer ratings around new offerings using the description of securities, ranking and subordination, covenants, refinancing structure, and use of proceeds. The corpus supports calibration of notching and recovery assumptions across the Canadian cross-border population.
Operational counterparties confirm the terms of securities they will administer: denominations, transfer restrictions, redemption mechanics, record-date conventions, and CDS-DTC settlement arrangements. For debt deals they review trust indentures, supplemental indentures, and event-of-default provisions filed as exhibits.
Compliance and surveillance teams at broker-dealers and SROs monitor MJDS issuance volumes and eligibility representations on the registration statement cover, tracking how the auto-effective pathway is used and whether registrants meet home-jurisdiction reporting conditions.
Data engineering teams and AI vendors ingest filer CIK, accession metadata, exhibit inventories, and Inline XBRL fee-table tags to build new-issue calendars, league-table reconstructions, and fee-pool analytics. The EX-FILING FEES exhibit is the structured anchor: it standardizes security-type classifications and aggregate offering amounts. RAG and LLM developers ground cross-border securities assistants on the prospectus and exhibit text.
Vendors building precedent-clause databases populate searchable libraries of MJDS underwriting agreements, opinions, and prospectus sections, surfacing clause-level comparisons for plan-of-distribution, taxation, eligibility, and enforcement-of-judgments language. Filer, date, exhibit type, and fee-data metadata drive faceted search.
The Form F-10EF Files Dataset supports a small number of concrete cross-border capital markets workflows. Each use case below ties to specific record components — the registration statement body, named exhibit families, the EX-FILING FEES Inline XBRL document, or metadata.json fields.
Capital markets bankers at bulge-bracket and Canadian dealers query the corpus to find recent precedents for bought deals, ATM programs, and base-shelf debt takedowns by comparable Canadian issuers. They filter entities[].sic and stateOfIncorporation to narrow to peer subsectors (e.g., A6 Ontario gold miners or A1 Alberta E&P), then pull the prospectus body for greenshoe sizing, stabilization language, and use-of-proceeds, and read EX-1.1 underwriting agreements for gross spread grids, market-out triggers, and lock-up scope. Output is a structured precedent table feeding pitch books and term-sheet drafting.
Compliance analysts at broker-dealers and SRO surveillance teams monitor how MJDS auto-effectiveness is used. They iterate F-10EF accessions filed each month, extract MJDS basis statements and Rule 467(b) representations from the registration statement cover, and join them to entities[].fileNo lineage of 333-... shelves to detect issuers that lose 12-month reporting history or fall below float thresholds mid-shelf. The output is an exception list flagging eligibility risk before a takedown.
Cross-border securities lawyers and underwriters' counsel build clause libraries from the prospectus and exhibits. They section-segment the F-10EF body to extract enforceability-of-judgments risk factors, plan-of-distribution mechanics, and Canadian-tax disclosure, and parse EX-5 validity opinions and EX-8 tax opinions for opinion qualifications, assumptions, and reliance language. Joined against documentFormatFiles[].type filters, the result is a faceted, firm-tagged template database used in drafting and negotiation.
Equity capital markets data teams and league-table providers extract ffd:-namespaced facts (ffd:FormTp, ffd:FeeRate, security type, proposed maximum aggregate offering price, offset amounts, prior 333- references) from the EX-FILING FEES Inline XBRL exhibit. Aggregating these across accessions produces normalized cross-border shelf-capacity, fee-pool, and carry-forward analytics by issuer, security type, and underwriter, and feeds new-issue calendars and league-table reconstructions without HTML scraping of the rendered fee table.
Audit firm capital markets desks and legal-research teams track which firms appear on which MJDS deals. They iterate EX-23.x consents to identify the issuer's auditor, predecessor auditor, and reserves or qualified-person experts (NI 43-101, NI 51-101), and EX-8.x tax opinions to identify Canadian and U.S. tax counsel. Combined with entities[].sic and filedAt, this produces firm-level market-share dashboards across the MJDS issuer population, used for pitch positioning and conflict checks.
Credit analysts and rating agency teams covering Canadian cross-border debt issuers parse EX-4.x indentures, supplemental indentures, and forms of note, plus EX-25 Form T-1 trustee statements. They extract ranking and subordination, restricted-payments baskets, change-of-control puts, negative-pledge carve-outs, and event-of-default thresholds, joined to co-registrant guarantor blocks in entities[] to map the guarantor perimeter. The output supports notching, recovery, and covenant-quality scoring for new-issue allocation and surveillance.
Legal-tech vendors and AI teams building cross-border securities copilots use the dataset as grounded training and retrieval material. They strip the SGML <DOCUMENT> envelope from each HTML, segment by exhibit type, and pair section text with structured anchors from metadata.json (form type, accession, filer CIK, file number, filing timestamp) and ffd: fee-table facts. The result is a labeled MJDS corpus for clause classifiers, prospectus-summarization models, and RAG indexes that answer questions about Canadian cross-border offerings with cited exhibit-level provenance.
The Form F-10EF Files Dataset is available through three access methods: a metadata index API, a full dataset archive download, and per-container downloads. The dataset covers F-10EF filings from May 2007 to the present, packaged as monthly ZIP containers that hold a metadata JSON file plus the original EDGAR submission documents (HTML, TXT) for each accession number.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-f10ef-files.json
This endpoint returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, total record and size counters, form types covered, container format, and file types) along with the full list of monthly container files. Each container entry includes its key, size, record count, last updated timestamp, and a direct download URL. Poll this endpoint to detect which containers were refreshed in the latest run and fetch only those that changed. No API key is required to access the index.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a4d-8e59-0490484b7be7",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-f10ef-files.zip",
4
"name": "Form F-10EF Files Dataset",
5
"updatedAt": "2026-05-05T02:48:21.984Z",
6
"earliestSampleDate": "2007-05-01",
7
"totalRecords": 231,
8
"totalSize": 2929581,
9
"formTypes": ["F-10EF"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "JSON", "TXT"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-f10ef-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 13818783,
17
"records": 154,
18
"updatedAt": "2026-03-21T02:51:19.000Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-f10ef-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every monthly container from May 2007 onward. This endpoint requires a valid API key supplied via the token query parameter. The full archive is compact, so a one-shot download is practical for most use cases.
Download Single Container: https://api.sec-api.io/datasets/form-f10ef-files/2026/2026-03.zip?token=YOUR_API_KEY
Each container is a monthly ZIP archive following the path pattern <YEAR>/<YEAR>-<MONTH>.zip. Use this endpoint to fetch only the months you need or to incrementally pull containers flagged as updated by the index API. This endpoint requires an API key supplied via the token query parameter.
The dataset covers Form F-10EF, the auto-effective variant of Form F-10. F-10EF is a Securities Act of 1933 registration statement filed by Canadian issuers eligible to use the MJDS, with effectiveness occurring immediately on filing under Rule 467(b) rather than awaiting SEC staff review.
One record represents a single SEC accession — one F-10EF submission filed on EDGAR by a Canadian MJDS-eligible issuer. Each record is delivered as an accession-numbered folder that bundles the registration statement HTML, every text-bearing exhibit HTML, the Inline XBRL EX-FILING FEES exhibit (when required), and a metadata.json index that mirrors the EDGAR submission header.
The filer is the Canadian issuer itself, acting as a foreign private issuer. Eligibility requires Canadian incorporation, foreign private issuer status under Rule 405, at least 12 months of Canadian reporting history with current continuous disclosure, and — for most equity offerings — a public float of at least US$75 million held by non-affiliates. Co-registrant guarantor subsidiaries may sign alongside the principal Canadian issuer for guaranteed-debt offerings.
EDGAR-based F-10EF records in this dataset begin in May 2007 and continue through the present, packaged as monthly ZIP containers.
The dataset is distributed as monthly ZIP containers. Each container expands into a flat directory of accession-numbered folders, each containing a metadata.json index and the SGML-wrapped HTML documents (registration statement, exhibits, and the Inline XBRL filing-fee exhibit when applicable). The dataset's declared file types are HTML, JSON, and TXT.
Both forms share the same MJDS regime, the same eligible issuer population, and substantially identical prospectus content. The difference is procedural: a standard F-10 is filed for SEC staff review and becomes effective only upon SEC declaration under Rule 467(a), whereas F-10EF is auto-effective on filing under Rule 467(b). Most modern MJDS shelf registrations use F-10EF.
The EX-FILING FEES document is an Inline XBRL XHTML file that emits machine-readable ffd:-namespaced facts (form type, fee rate, security type, proposed maximum aggregate offering price, offset amounts, prior 333- references) under the SEC's Filing Fees Data taxonomy. Downstream extraction of fee-table data should rely on these XBRL facts rather than scraping the rendered HTML, because the facts are normalized and unambiguously typed. Earlier filings predating the EX-FILING FEES mandate carry only a calculation-of-registration-fee table on the registration statement cover and no separate Exhibit 107.