Home / APIs / Fund data
Fund proxies

Fund Reorganizations API: mergers, policy changes and votes in fund proxies

Fund proxy actions as JSON: participating funds, share classes, preferred shares, leverage, proposals, reorganizations, policy and structure changes.

Newfilling from 2020 onward
curl -H "Authorization: Bearer $SECFEED_KEY" \
  "https://secfeedapi.com/v1/fund-reorganizations?size=2"
import os, requests

r = requests.get(
    "https://secfeedapi.com/v1/fund-reorganizations",
    params={'size': '2'},
    headers={"Authorization": f"Bearer {os.environ['SECFEED_KEY']}"},
)
print(r.json())

Overview

Mutual funds, ETFs, closed end funds and BDCs file proxies when they need shareholder approval: to merge one fund into another, change a fundamental investment policy, switch to non diversified status, or convert a closed end fund. These proxies list the funds involved, their net assets and share classes, and what happens if the vote fails.

The Fund Reorganizations API returns one record per fund proxy with each fund and its role, every proposal with its type and vote standard, each reorganization with target and acquiring fund, costs and who bears them, and every policy and structure change.

What you get

Built for developers who would rather not parse EDGAR.

Funds involved

Each fund with ticker, type, role (target, acquiring or soliciting), net assets and shares.

Reorganizations

Target and acquiring fund, consideration, expected closing, tax treatment and costs.

Proposals

Type, applicable funds and classes, vote standard and the consequence if not approved.

Closed end detail

Preferred share series, preferred voting rights, leverage and asset coverage.

Endpoints

Authenticate with Authorization: Bearer YOUR_KEY. Responses are JSON.

GET|POST/v1/fund-reorganizationsReference →

Fund proxy actions: participating funds, share and preferred classes, leverage, proposals, reorganizations, policy changes and structural changes.

Parameters: ticker | cik, accessionNo, startDate, endDate, data.<path>=value, from, size (max 50)

Response fields

The main fields in every result. The raw filing data is always one level down.

FieldMeaning
accessionNo, filedAt, entitiesThe fund proxy and the registrant.
meetingDate, recordDate, registrantTypeThe meeting and the kind of fund.
funds[].fundName, ticker, role, netAssetsUSDEach fund in the proxy.
proposals[].proposalType, voteStandard, consequenceIfNotApprovedWhat is on the ballot.
reorganizations[].targetFund, acquiringFund, expectedClosingFund mergers.
reorganizations[].taxFree, costsUSD, costsBorneByTax treatment and who pays.
policyChanges[].policyTopic, changeType, proposedPolicyFundamental policy changes.
structureChanges[].changeType, effectiveDateConversions and diversification changes.
leverage[].assetCoverageRatioPct, preferredShares[].seriesClosed end fund leverage.

Use cases

Datasets behind this API

The SEC forms this API reads, with live filing counts.

FAQ

How far back does it go?

These datasets launched in October 2026 and are being filled newest first, starting with filings from 2020 onward. The live counter on this page shows what is loaded today. Older years are added after that.

How is the data produced?

Each record is extracted from the filing text by an AI model and validated against a fixed schema before it is published; see our AI Disclosure. A value the filing does not state is returned as null, never guessed.

Which filings are read?

DEF 14A proxies filed by registrants that also file fund reports such as N-CSR, N-CEN, N-PORT or 485BPOS.

Try the Fund Reorganizations API free

125 free API calls to start. No sales call.

Get free API key →