The Form CFPORTAL-W Files Dataset is a structured collection of every EDGAR submission of Form CFPORTAL-W (officially "Form Funding Portal Withdrawal of Registration"), the terminal filing through which an SEC-registered funding portal exits the Regulation Crowdfunding intermediary regime. Each record represents one complete withdrawal submission by one funding portal entity, identified by a unique EDGAR accession number and packaged as an accession-named folder containing the structured XML payload, the SEC-generated XHTML rendering, and a JSON metadata sidecar. Filings are made by funding portals registered under Section 3(a)(80) of the Securities Exchange Act of 1934 when they cease, or determine to cease, operating as a funding portal. Coverage begins in November 2016 — immediately after the first cohort of portals registered under Regulation Crowdfunding matured into the earliest withdrawals — and extends to the present, with monthly ZIP containers refreshed as new CFPORTAL-W filings are accepted by EDGAR.
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 CFPORTAL-W filing on EDGAR as a self-contained record, organized into calendar-month ZIP containers. Form CFPORTAL-W is the withdrawal counterpart to Form Funding Portal (CFPORTAL), the registration form that funding portals use to register with the SEC under Regulation Crowdfunding, the rulemaking adopted to implement Title III of the JOBS Act. A funding portal is a non-broker intermediary that operates an online platform for offerings of securities sold under the Section 4(a)(6) crowdfunding exemption. When such a portal ceases to operate as a funding portal, it must promptly file Form CFPORTAL-W; the withdrawal becomes effective thirty days after receipt by the Commission unless the staff acts otherwise. The form plays a closing-of-the-record function analogous to Form ADV-W for investment advisers and Form BDW for broker-dealers, and it is filed under the Securities Exchange Act of 1934 (the EDGAR act value for the filing entity is 34).
The form is short and predominantly structured. It captures the portal's identifying information, its form of organization, any direct or indirect controlling relationships, a uniform matrix of disciplinary, regulatory, civil, and financial-disclosure questions, escrow-arrangement details for investor funds, the executed signature block, and three numbered schedules (A, B, and D) capturing ownership at registration, amendments to that ownership since the prior filing, and the wind-down particulars specific to withdrawal. The dataset retains all documents from the original EDGAR submission with the exception of image files, which are stripped. CFPORTAL-W filings rarely carry attachments beyond the structured XML and its rendering, so individual records are small. The file types found in the dataset are XML, JSON, and PDF, with PDF appearing only when filers attach supplementary wind-down or successor documentation. CFPORTAL-W carries no XBRL or iXBRL data; this form was never within the structured-financials regime.
A single record in the Form CFPORTAL-W Files Dataset is one complete EDGAR submission of Form CFPORTAL-W, identified by a unique EDGAR accession number. Each record materializes as an accession-named folder (dashes stripped) inside a calendar-month ZIP container, and the folder bundles the structured XML payload of the form, the SEC-generated XHTML rendering of that payload, and a JSON metadata sidecar describing the EDGAR submission envelope. The unit of observation is the filing event — the act of a funding portal formally withdrawing its registration from the Commission — rather than the funding portal entity itself or any narrower disclosure subsection.
Each accession folder contains, at minimum, three artifacts:
metadata.json — a JSON sidecar summarizing the EDGAR submission header, the filer entities, and the documents that accompanied the filing.primary_doc.xml — the structured XML payload of the form itself, in the EDGAR crowdfunding namespace, carrying every disclosure field the filer answered.xslCFPORTAL_X01/primary_doc.xml — despite the .xml extension and the parallel filename, this file is an XHTML 1.0 Strict document produced by EDGAR's xslCFPORTAL_X01 XSL transform, providing the human-readable rendered form with labels, inline CSS, and the OMB control header.metadata.json sidecarThe metadata sidecar is a JSON object that mirrors the EDGAR submission envelope rather than the form's substantive disclosures. The fields carried for every record include:
formType — constant value CFPORTAL-W.accessionNo — canonical dashed accession number (e.g. 0001898740-25-000001).filedAt — ISO-8601 acceptance timestamp with timezone offset.description — filer-supplied free-text label, frequently the boilerplate Form CFPORTAL-W -.linkToFilingDetails, linkToTxt, linkToHtml — URLs pointing to the XSLT-rendered primary document, the full SGML .txt submission, and the EDGAR submission index page on sec.gov respectively.linkToXbrl — empty for this form type.documentFormatFiles — an array of document descriptors, each with sequence, size, documentUrl, and type. Three entries appear consistently: the XSLT-rendered XML, the raw primary_doc.xml, and the complete SGML submission text file.entities — an array of filer-entity descriptors. Each entry includes the 10-digit cik, companyName (suffixed with the role tag, e.g. (Filer)), fileNo (the SEC file number, formatted 007-NNNNNN for funding portals), fiscalYearEnd (MMDD), stateOfIncorporation, act (34), filmNo, and a per-entity type value of CFPORTAL-W.seriesAndClassesContractsInformation — empty for CFPORTAL-W.dataFiles — empty for CFPORTAL-W.id — an opaque dataset-internal 32-hex identifier.This sidecar is the canonical source for filing-level identifiers, timing, and document inventory; the form payload itself does not carry the accession number or the EDGAR acceptance time.
primary_doc.xml)The structured payload is an XML document whose root is <edgarSubmission> in the namespace http://www.sec.gov/edgar/crowdfunding, with the com: prefix bound to http://www.sec.gov/edgar/common for shared address and personal-name elements. The document is partitioned into two top-level branches: <headerData>, which carries EDGAR routing and credential metadata, and <formData>, which carries the substantive disclosures.
<headerData>submissionType — constant CFPORTAL-W.filerInfo / filer / filerCredentials — the filer's filerCik (10-digit, zero-padded) and filerCcc (the EDGAR CIK Confirmation Code, redacted to XXXXXXXX in publicly disseminated copies).filerInfo / flags — boolean routing flags such as returnCopyFlag and overrideInternetFlag.<formData> — the substantive disclosure bodyThe form body is organized into a fixed sequence of structured groups. Address blocks throughout reuse the shared common-namespace elements com:street1, com:street2, com:city, com:stateOrCountry, and com:zipCode, and personal-name blocks reuse com:prefix, com:firstName, com:middleName, and com:lastName.
identifyingInformation — the funding portal's legal name, prior trade names, public website, IRS Employer Identification Number, principal office address, mailing address (when distinct), primary contact telephone and email, the contact employee's structured name and title, fiscal-year-end month-day, and the yes/no flags anyPreviousRegistrations and anyForeignRegistrations.formOfOrganization — legalStatusForm (free-text legal form such as Limited Liability Company, Corporation, Limited Partnership), jurisdictionOrganization (state or country code), and dateIncorporation formatted MM-DD-YYYY.successions — the isSucceedingBusiness Y/N flag and, where the portal is a successor, optional details identifying the predecessor entity.controlRelationships — one or more <fullLegalNames><fullLegalName> entries enumerating the natural persons or entities that control, or are controlled by, the funding portal.disclosureAnswers — a uniform yes/no flag matrix grouped into four parallel subgroups: criminalDisclosure (felony convictions, false-statement findings, and similar), regulatoryActionDisclosure (SEC, CFTC, state, SRO, and foreign regulatory actions), civilJudicialActionDisclosure (injunctions and securities-related civil findings), and financialDisclosure (bankruptcy, receivership, unsatisfied judgments, bonding-company actions). Each subgroup contains a battery of boolean fields with names such as isConvictedOfFelony, isMadeFalseStatement, isEnjoined, and hasSubjectOfBankruptcy. Affirmative answers are typically accompanied by free-text explanations or by attached disclosure-reporting pages.nonSecuritiesRelatedBusiness — the isEngagedInNonSecurities flag plus supporting descriptive text where the portal conducts other lines of business.escrowArrangements — one or more investorFundsContacts blocks naming the qualified third party (typically a bank) holding investor funds, with bank name, address, and phone, plus a free-text compensationDesc describing the portal's compensation arrangements.execution — the closing signature block: executionDate formatted MM-DD-YYYY, the fullLegalNameFundingPortal, and the signing person's personSignature and personTitle.The form's schedules sit inside <formData> alongside the narrative groups and carry the most analytically dense structured data:
scheduleA — one <entityOrNaturalPerson> block per direct owner or executive officer at the time of original registration. Each block contains fullLegalName, entityType (NP natural person, DE domestic entity, FE foreign entity), titleStatus (e.g. CEO, manager, member), dateOfTitleStatusAcquired formatted MM/YYYY, ownershipCode (a single letter A through E representing ownership tiers from less than 5% through 75% or more), and a controlPerson Y/N flag.scheduleB — the amendment companion to Schedule A, expressed as <amendEntityOrNaturalPerson> entries with the same fields plus typeOfAmendment (A for additions and analogous codes for removals or modifications). Schedule B captures every change to the ownership/officer roster since the prior CFPORTAL filing, including changes that occurred during the wind-down period.scheduleD — the withdrawal-specific schedule. Its fields define the cessation event itself: dateBusinessCeasedWithdrawn is the date the portal ceased operating; a bookKeepingDetails block specifies where the books and records will be retained after withdrawal, with bookKeepingEntityName, bookKeepingEntityType (codes such as BO for the books-and-records keeper), isAddressPrivateResidence, the structured location address, and bookKeepingLocationDesc; and three Y/N flags — isInvestigated, investorInitiatedComplaint, and privateCivilLitigation — disclose whether the portal is the subject of any pending investigation, customer complaint, or private civil action at the time of withdrawal.Schedule D is the diagnostic content unique to the withdrawal form. Where Schedules A and B mirror the corresponding schedules of Form CFPORTAL, Schedule D exists only on CFPORTAL-W and is the anchor for any analysis of the wind-down event itself.
The third file in each record — located at xslCFPORTAL_X01/primary_doc.xml despite its misleading extension — is the XHTML 1.0 Strict rendering produced by EDGAR's stylesheet. It contains a full <!DOCTYPE html ... XHTML 1.0 Strict ...> declaration, inline CSS, and human-readable form headings such as "Form Funding Portal Filer Information", "Filer CIK", "OMB APPROVAL", and the standard "Estimated average burden hours per response" notice. The rendered document carries no information beyond what is in primary_doc.xml; it exists for visual inspection and printing rather than for structured parsing. Treating it as XML will fail because its content model is XHTML.
For every accession in the dataset, the record includes:
metadata.json),primary_doc.xml),xslCFPORTAL_X01/primary_doc.xml,Image files attached to the original EDGAR submission are excluded. The full SGML .txt submission file is not redistributed inside the accession folder, although its sec.gov URL is preserved in metadata.json under linkToTxt, and its byte size and document type are listed in documentFormatFiles. The CIK Confirmation Code (filerCcc) is redacted to XXXXXXXX in disseminated copies, consistent with EDGAR's standard handling of authentication credentials.
Form CFPORTAL-W came into existence with the adoption of Regulation Crowdfunding, which became effective on May 16, 2016, with funding-portal registration opening on January 29, 2016; the dataset's coverage begins in November 2016, immediately after the first wave of registrations matured into the earliest withdrawals. From inception, EDGAR has accepted CFPORTAL-W exclusively as a structured XML submission accompanied by an SEC-generated XSLT rendering. There was no ASCII text era and no HTML-only era for this form type; it has been delivered in the same XML-plus-XHTML pairing across the dataset's full history. The schema namespace http://www.sec.gov/edgar/crowdfunding and the common-element namespace http://www.sec.gov/edgar/common have remained stable, and the high-level partition into <headerData> and <formData> with the identifyingInformation, formOfOrganization, successions, controlRelationships, disclosureAnswers, nonSecuritiesRelatedBusiness, escrowArrangements, execution, scheduleA, scheduleB, and scheduleD groupings has been preserved across vintages. As a consequence, panel analyses across the November 2016 to present horizon can rely on a single XML schema without era-specific branching.
A few practical points matter for working with the records:
metadata.json and as the dash-stripped folder name within the monthly container.primary_doc.xml; the XHTML sibling is a presentation artifact and should not be parsed as XML.MM-DD-YYYY for dateIncorporation and executionDate, MM/YYYY for dateOfTitleStatusAcquired, MMDD for fiscalYearEnd in metadata.json, and ISO-8601 for filedAt. These formats are stable but inconsistent across fields, so consumers must apply field-specific parsers.dateBusinessCeasedWithdrawn is the analytically central date for cessation-event studies, while filedAt records when the filing reached EDGAR and the regulatory thirty-day clock began. The two dates can differ materially.disclosureAnswers is exhaustive and uniform, so a Y in any field is rare and informative; affirmative answers should be cross-referenced against the narrative explanation text and any attached disclosure-reporting pages.entities array of metadata.json when a successor or related party is named, even though the structured form payload is centered on the withdrawing portal.Form CFPORTAL-W is filed by an SEC-registered funding portal to withdraw its own registration. Each accession number represents one withdrawal filing by one funding portal entity. The form is the operational mechanism by which a funding portal exits the Regulation Crowdfunding intermediary regime.
A funding portal is the class of crowdfunding intermediary defined in Section 3(a)(80) of the Securities Exchange Act of 1934: a person intermediating securities transactions made solely under the Section 4(a)(6) crowdfunding exemption, which does not offer investment advice, solicit purchases, compensate solicitors per transaction, or hold investor funds or securities. In practice, registrants are small, non-broker-dealer LLCs or corporations operating online platforms for Regulation Crowdfunding offerings.
The withdrawal is filed by the funding portal entity itself, not by issuers using the portal, investors, or associated persons. Only entities that previously completed a registration on Form Funding Portal (Form CFPORTAL) appear in this filer population.
Form CFPORTAL-W is event-driven, not periodic. The obligation arises when a registered funding portal ceases, or determines to cease, acting as a funding portal. Rule 400(e) of Regulation Crowdfunding (17 CFR 227.400(e)) requires the entity to file the withdrawal "promptly" upon that cessation. There is no annual or quarterly schedule, and a portal that continues to operate never files this form.
Common underlying causes include voluntary wind-down, merger, transfer of the platform business, dissolution of the entity, pivot away from Regulation Crowdfunding intermediation, and loss or termination of FINRA membership (which is a precondition for funding portal status).
Two timing concepts apply:
During the 30-day pendency period, the registration remains in place and the portal stays subject to SEC and FINRA jurisdiction over prior conduct. The form is filed once per withdrawal event; a portal seeking to re-enter the regime later must file a new initial Form CFPORTAL, not rescind the withdrawal.
Title III of the JOBS Act (2012) created the Section 4(a)(6) crowdfunding exemption and the funding portal concept in Exchange Act Section 3(a)(80). Section 3(h) directed the Commission to exempt funding portals from broker-dealer registration if they register with the Commission and join a national securities association (FINRA in practice). The Commission implemented this through Regulation Crowdfunding, effective May 16, 2016, with funding portal registration accepted starting January 29, 2016. Within that regulation, Rule 400 governs the registration lifecycle: initial registration (CFPORTAL), amendments (CFPORTAL/A), and withdrawal (CFPORTAL-W).
Within the funding portal lifecycle on EDGAR:
A withdrawing portal cannot substitute a final CFPORTAL/A for CFPORTAL-W. Conversely, a portal restructuring but continuing to intermediate Regulation Crowdfunding offerings should amend rather than withdraw.
The CFPORTAL-W filer population is therefore narrowly limited to entities holding an active SEC funding portal registration at the moment they decide to exit, regardless of whether they ever hosted a completed Regulation Crowdfunding offering.
Because funding portal registration only began January 29, 2016, no CFPORTAL-W filing predates 2016. The form, the underlying regime, and EDGAR acceptance all start in the same year, and the earliest filings in this dataset date to late 2016, reflecting the first cohort of portals that ceased operations within months of launch. All records are native EDGAR submissions, with no paper-era predecessor.
Form CFPORTAL-W is the terminal filing in the funding-portal registration lifecycle under Regulation Crowdfunding. The most useful comparisons fall into three groups: the other CFPORTAL-family forms that bracket the same registrant, parallel withdrawal forms used by other SEC-registered intermediaries, and the issuer-side Regulation Crowdfunding filings that share the same statute but a different filer population.
Form CFPORTAL opens the same registration that CFPORTAL-W closes. Both are filed by the same entity, share the 7-series SEC file numbers assigned to funding portals, and use overlapping XML schedules for identifying information.
The substantive gap is large. CFPORTAL is a populating filing: legal and business names, organizational form, jurisdiction, control persons, direct and indirect owners (Schedules A/B), disciplinary history, compensation types, and third-party service providers. CFPORTAL-W is a closing filing: cessation date, disposition of books and records, custody arrangements after wind-down, and any successor information. A complete portrait of any single funding portal requires both, plus any intervening amendments.
CFPORTAL/A and CFPORTAL-W are separated by operating status. CFPORTAL/A maintains an active registration, can be filed many times, and carries the full schedule structure of CFPORTAL. CFPORTAL-W terminates the registration, is filed once, and is brief. Reconstructing a portal's regulatory history requires the chain of CFPORTAL and CFPORTAL/A filings to track evolving disclosures and the CFPORTAL-W to mark the endpoint.
BDW is the structural analog of CFPORTAL-W in the broker-dealer regime under Section 15 of the Exchange Act. Both are terminal intermediary filings, both rely on the 30-day-after-receipt effectiveness convention, and both ask about books-and-records custody and reasons for withdrawal.
The forms diverge sharply on disclosure depth because the underlying activity does. BDW solicits pending customer claims, arbitrations, unsatisfied judgments, securities and money held for customers, and SRO-membership terminations across FINRA, exchanges, and the MSRB. None of these apply to funding portals: Rule 402 of Regulation Crowdfunding bars portals from holding investor funds or securities and from the broader activities that drive BDW's content. Filer populations are largely disjoint.
ADV-W is also a terminal intermediary filing, but it operates under the Investment Advisers Act, uses Form ADV's Part 1A item structure, and concerns clients and assets under management. Its custody disclosures are more developed because advisers can take custody of client assets, while funding portals cannot. ADV-W is a useful design comparable for understanding withdrawal-form architecture, but content and filer populations do not overlap with CFPORTAL-W.
TA-W deregisters a transfer agent under Section 17A of the Exchange Act and, like CFPORTAL-W, is a brief terminal filing covering reasons for ceasing operations, record disposition, and successor information. The subject matter differs entirely: TA-W concerns custody and transfer of issuer securityholder records to a successor transfer agent; CFPORTAL-W concerns the disposition of investor and offering records tied to previously hosted Regulation Crowdfunding offerings. Different schedules, different regulatory regime.
Form C-TR is the most easily confused filing because it shares the Regulation Crowdfunding statutory home. The distinction is categorical: C-TR is filed by an issuer of crowdfunded securities to terminate its Form C-AR annual-report obligation under Rule 202 (triggered by holder-of-record counts, asset thresholds, repurchase of all securities, or dissolution). CFPORTAL-W is filed by the funding portal itself to terminate its registration when the portal ceases operating. Same regime, opposite sides of the platform.
These are the issuer-side reporting backbone of Regulation Crowdfunding: offering statement (Form C), progress update (Form C-U), and annual report (C-AR). They contain offering terms, financial statements, use of proceeds, risk factors, and ongoing issuer operating disclosures. None of this content appears in CFPORTAL-W. The natural intersection is operational: a CFPORTAL-W filing signals that an intermediary is no longer available to host new Form C offerings, with downstream effects on issuers that relied on the closing portal. Complementary, not substitutable.
Form 15-12B, Form 15-12G, and Form 15-15D terminate registration of a class of securities under Section 12(b) or Section 12(g) or suspend reporting under Section 15(d). They are styled as termination filings, which invites confusion, but the substance is unrelated: Form 15 deregisters a securities class and ends an issuer's periodic reporting; CFPORTAL-W deregisters an intermediary entity from funding-portal status under Rule 400. Holder counts and security-class fields on Form 15 have no analog on CFPORTAL-W's portal CIK, file number, cessation date, and successor fields.
Three narrow attributes make CFPORTAL-W distinct and non-substitutable. The filer population is restricted to entities that are or were SEC-registered funding portals, a small and well-defined universe. The trigger is cessation of funding-portal operations specifically, not a broader corporate event, securities-class deregistration, or issuer-reporting termination. The content is terminal and wind-down-focused: cessation date, record disposition, successor arrangements, and the formal withdrawal request under Rule 400.
CFPORTAL opens the regime, CFPORTAL/A maintains it, CFPORTAL-W closes it. BDW, ADV-W, and TA-W are structurally similar terminal filings in adjacent intermediary regimes. C-TR and the Form C family cover the issuer side of the same statute. Form 15 deregisters securities classes rather than intermediaries. Reach for CFPORTAL-W when the question is the exit of a Regulation Crowdfunding intermediary; pair it with adjacent datasets only when the question crosses populations or lifecycle stages.
Form CFPORTAL-W records mark the formal exit of funding portals registered under Regulation Crowdfunding. Different professionals draw on distinct fields: Schedule D cessation date and wind-down narrative, Schedule A and B control-person disclosures, CIK and SEC file number, disciplinary disclosure flags, and the books-and-records retention party.
Used to track portal attrition. They join the Schedule D cessation date and stated reason for withdrawal with prior CFPORTAL registrations to compute portal lifespans, survival curves, and exit cohorts that feed policy commentary on Title III intermediary stability.
Used to reconcile internal registration rosters with the public EDGAR record. CIK and SEC file number anchor entity identity; the effective withdrawal date drives examination-file closure; the books-and-records retention party routes post-exit inquiries; and the disciplinary disclosure flags surface withdrawals filed alongside enforcement events.
Used as the authoritative source for portal exits in crowdfunding sector reports. Schedule A and B disclosures track which control persons have left the regulated portal space, cessation dates time exits against issuer offering activity, and successor statements flag transferred relationships, supporting market sizing and concentration briefings.
Used as drafting precedent and compliance reference. Counsel review peer wind-down narratives, treatment of investor-funds custody and books-and-records retention, and answers to disciplinary disclosure questions to advise clients on orderly exit, retention obligations, and coordination with SRO membership termination and any pending offerings.
Used to confirm the regulatory status of a target. CIK, SEC file number, effective withdrawal date, successor disclosure, and disciplinary flags feed closing checklists, clean-exit representations, transition services agreements, and books-and-records custody terms between buyer and seller.
Used to verify and contextualize portal closures. Reporters pull the cessation date, wind-down language, Schedule A and B control persons, and disciplinary flags for shutdown coverage, investigations into portals exiting under regulatory pressure, and longer-form pieces on the Title III intermediary market.
Used as a structured panel of intermediary exits from November 2016 onward. Scholars link withdrawal events to issuer-level offering data via portal CIK to study post-exit issuer outcomes, the signaling content of disciplinary disclosures at withdrawal, and the relationship between control-person turnover and portal survival.
Used as a status-change feed. Engineers parse the structured filing to flip registry status on withdrawal, write the effective withdrawal date into entity records, persist the books-and-records custodian as a long-lived contact, and version control-person changes for downstream search APIs and intermediary-status checks.
Used by payment processors, escrow providers, transfer agents, broker-dealers, and software vendors integrated with funding portals to monitor counterparty status. Cessation date and successor disclosure trigger contract termination, fund-flow redirection, and records transfer; disciplinary flags inform vendor-risk reviews of principals named in Schedules A and B.
Used by broker-dealers active in Reg CF or sharing principals with funding portals to track affiliate exits. Schedule A and B control-person disclosures are reconciled against associated-person rosters and Form U4/Form U5 records to keep firm-level disclosures and supervisory controls consistent with the portal's withdrawal.
The following workflows are grounded in the structured XML payload and the EDGAR submission envelope of each Form CFPORTAL-W record.
Building a funding-portal exit registry. Pair entities[].cik and fileNo from metadata.json with scheduleD/dateBusinessCeasedWithdrawn and filedAt to flip portal status from active to withdrawn in an internal intermediary database, persist the 30-day effectiveness clock, and version the record at each new CFPORTAL-W submission. The output is a status-change feed for downstream search APIs and counterparty-monitoring dashboards.
Computing portal survival and attrition curves. Join CFPORTAL-W cessation dates against the corresponding CFPORTAL registration filings on portal CIK to build per-portal lifespans, then aggregate into cohort survival curves by registration year, jurisdiction (formOfOrganization/jurisdictionOrganization), or legal form (legalStatusForm). Feeds Reg CF policy commentary and academic studies of Title III intermediary stability.
Flagging withdrawals filed under regulatory pressure. Scan disclosureAnswers (criminal, regulatory-action, civil-judicial, and financial subgroups) and scheduleD flags isInvestigated, investorInitiatedComplaint, and privateCivilLitigation for any Y answer, then cross-reference the narrative explanations and any attached PDF disclosure-reporting pages. Supports enforcement-tracking workstreams at the SRO, journalism on troubled-portal closures, and vendor-risk reviews of named principals.
Routing post-exit records and inquiries. Extract the bookKeepingDetails block — bookKeepingEntityName, bookKeepingEntityType, bookKeepingLocationDesc, and the structured custodian address — to populate a long-lived contact record for the portal after withdrawal. Used by regulators to direct examination follow-ups, by counterparties to retrieve transaction records, and by acquirers to confirm books-and-records custody terms in transition services agreements.
Tracking control-person mobility across the regulated portal space. Iterate scheduleA/entityOrNaturalPerson and scheduleB/amendEntityOrNaturalPerson entries (with fullLegalName, titleStatus, ownershipCode, controlPerson flag, and typeOfAmendment) across all CFPORTAL-W filings to identify principals exiting funding-portal status. Reconciled against Form U4/U5 records and broker-dealer associated-person rosters to keep affiliate disclosures and supervisory controls consistent.
Drafting precedent for orderly portal wind-downs. Securities counsel pull peer CFPORTAL-W filings to compare narrative compensationDesc text, escrowArrangements/investorFundsContacts treatment, books-and-records retention language, and successor identifications in successions. The output is a precedent bank that informs client wind-down plans, SRO membership-termination coordination, and disposition of pending Form C offerings hosted by the closing portal.
Quantifying issuer impact of intermediary exits. Link the cessation date to issuer-side Form C, C-U, and C-AR filings that named the withdrawing portal as intermediary, to measure how many active offerings were stranded at exit and to study post-exit issuer outcomes. Combines CFPORTAL-W's portal CIK with the Form C population to support market-concentration briefings and academic work on intermediary failure spillovers.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-cfportalw-files.json
The dataset index endpoint returns metadata describing the Form CFPORTAL-W Files Dataset, including its name, description, last update timestamp, earliest sample date, total record count and total size, covered form types, container format, and the file types included in each container. It also provides the download URL for the full dataset archive and a list of all individual container files with their size, record count, last updated timestamp, and per-container download URL. Polling this endpoint is the recommended way to monitor which containers were modified in the most recent refresh run, so you can selectively download only the containers that changed on a given day. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a42-a9ab-2671841f7866",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-cfportalw-files.zip",
4
"name": "Form CFPORTAL-W Files Dataset",
5
"updatedAt": "2026-04-16T08:40:27.252Z",
6
"earliestSampleDate": "2016-11-01",
7
"totalRecords": 87,
8
"totalSize": 6083761,
9
"formTypes": ["CFPORTAL-W"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["XML", "JSON", "PDF"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-cfportalw-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 138783,
17
"records": 2,
18
"updatedAt": "2026-04-16T08:40:27.252Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-cfportalw-files.zip?token=YOUR_API_KEY
Use this URL to download the complete archive containing every Form CFPORTAL-W filing from November 2016 to the present in a single ZIP file. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-cfportalw-files/2026/2026-03.zip?token=YOUR_API_KEY
Individual monthly containers can be downloaded directly without retrieving the full archive, which is useful for incremental updates or backfilling specific time ranges. This endpoint requires an API key.
The dataset covers Form CFPORTAL-W, officially "Form Funding Portal Withdrawal of Registration." It is the terminal filing through which an SEC-registered funding portal exits the Regulation Crowdfunding intermediary regime under Rule 400(e) of Regulation Crowdfunding (17 CFR 227.400(e)).
One record represents a single complete EDGAR submission of Form CFPORTAL-W by one funding portal entity, identified by a unique EDGAR accession number. Each record materializes as an accession-named folder containing metadata.json, the structured primary_doc.xml payload, and the SEC-generated XHTML rendering at xslCFPORTAL_X01/primary_doc.xml.
Only SEC-registered funding portals — entities that previously completed a registration on Form Funding Portal (CFPORTAL) and are defined under Section 3(a)(80) of the Securities Exchange Act of 1934 — file Form CFPORTAL-W, and only when they cease, or determine to cease, operating as a funding portal. Issuers, investors, broker-dealers, investment advisers, and transfer agents do not file this form.
The withdrawal becomes effective 30 days after the Commission receives the filing, unless the SEC institutes a proceeding to suspend or revoke the registration or otherwise delays effectiveness. During the 30-day pendency period the registration remains in place and the portal stays subject to SEC and FINRA jurisdiction over prior conduct.
The dataset begins with filings dated November 2016 — immediately after the first cohort of portals registered following the January 29, 2016 opening of funding-portal registration matured into the earliest withdrawals — and extends to the present. No CFPORTAL-W filing predates 2016 because the underlying regime did not exist before then.
The dataset is distributed as monthly ZIP containers. Each container holds one folder per accession, and the file types found inside are XML (the structured primary_doc.xml and the XHTML-rendered counterpart), JSON (the metadata.json envelope sidecar), and PDF (only when filers attach supplementary wind-down or successor documentation). The dataset carries no XBRL or iXBRL data.
Both filings live within Regulation Crowdfunding, but they sit on opposite sides of the platform. Form C-TR is filed by an issuer of crowdfunded securities to terminate its Form C-AR annual-report obligation under Rule 202; Form CFPORTAL-W is filed by the funding portal itself to terminate its SEC registration under Rule 400 when the portal ceases operating.