Severance and Change in Control API: potential payments to executives
What named executives get on termination or a change in control: payments by scenario, severance terms, pensions, deferred pay and separations.
curl -H "Authorization: Bearer $SECFEED_KEY" \ "https://secfeedapi.com/v1/severance-change-in-control?ticker=AAPL"
import os, requests
r = requests.get(
"https://secfeedapi.com/v1/severance-change-in-control",
params={'ticker': 'AAPL'},
headers={"Authorization": f"Bearer {os.environ['SECFEED_KEY']}"},
)
print(r.json())Overview
Proxy statements include a potential payments table: what each named executive would receive if fired without cause, after a change in control, on death or disability. Around it the proxy describes the agreements behind those numbers, the pension and deferred compensation tables, and any separation agreements with executives who left.
The Severance and Change in Control API returns each scenario row with cash severance, bonus, equity acceleration, benefits and total, plus the terms of each arrangement: severance and CIC multiples, single or double trigger, excise tax treatment and restrictive covenants.
What you get
Built for developers who would rather not parse EDGAR.
One row per executive and scenario, with the stock price and date the table assumes.
Severance and CIC multiples, trigger type, protection period and benefits continuation.
Pension benefits, SERPs and nonqualified deferred compensation balances.
Agreements with departing executives: dates, cash severance and consulting terms.
Endpoints
Authenticate with Authorization: Bearer YOUR_KEY. Responses are JSON.
What named executives stand to receive on termination or a change in control, plus retirement, deferral and separation arrangements.
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.
| Field | Meaning |
|---|---|
accessionNo, filedAt, entities | The proxy statement and the company. |
potentialPayments.asOfDate, stockPriceUSD | The assumptions behind the table. |
potentialPayments.payments[].executiveName, scenario | Who and which event. |
payments[].cashSeveranceUSD, equityAccelerationUSD, totalUSD | Amounts for that scenario in USD. |
severanceArrangements[].arrangementType, severanceMultiple, cicMultiple | The agreement or plan and its multiples. |
severanceArrangements[].cicTriggerType, exciseTaxTreatment | Single or double trigger and how parachute taxes are handled. |
pensionBenefits[].presentValueUSD, deferredCompensation[].aggregateBalanceUSD | Retirement and deferred pay values. |
separationAgreements[].executiveName, departureDate, cashSeveranceUSD | Departures and what was paid. |
Use cases
- Estimate executive payouts in a sale of the company
- Compare CIC multiples and trigger types across peers
- Track separation pay for departing executives
- Review pension and deferred pay obligations
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.
What scenarios are covered?
The ones the table shows, such as without cause, good reason, change in control with termination, death and disability. scenarioLabel keeps the filing's own wording.
Try the Severance and CIC API free
125 free API calls to start. No sales call.