Read this page with Option Symbols and Contract Identity, Contracts, Market Data Corrections and Missing Data, Historical Options Data API, and Backtesting Data Quality Checklist.
Corporate actions can change what an option contract represents. A split, merger, special dividend, spinoff, liquidation, bankruptcy event, or symbol change can alter deliverables, contract size, settlement behavior, or the option symbol used by market participants.
Use this guide when building contract validation, sizing, backtesting, or support workflows for adjusted options.
Quick answer
Do not assume every equity option contract represents exactly 100 shares of the current underlying ticker. Standard contracts commonly do, but corporate actions can create adjusted contracts with different deliverables. Use contract reference fields such as shares_per_contract, additional_underlyings, correction, as_of, and the full option ticker before sizing a trade, calculating PnL, or replaying history.
What can change
| Corporate action | Possible option-data effect |
|---|---|
| Forward or reverse split | Strike, deliverable, contract multiplier, or symbol can change. |
| Merger or acquisition | Deliverable can become cash, shares of another security, or a mixed package. |
| Special dividend or distribution | Deliverable or strike can be adjusted. |
| Spinoff | Contract can include additional underlying components. |
| Bankruptcy or liquidation | Settlement and expiration handling can change. |
| Symbol change | Underlying or option symbol can change while historical identity remains important. |
The exact adjustment is contract-specific. OCC information memos are the authoritative place to review many contract-adjustment events, while API reference fields are the application record your system needs to store.
Why adjusted options break naive systems
Naive systems usually hard-code three assumptions:
- One contract equals 100 shares.
- The current underlying ticker is the only deliverable.
- A parsed symbol is enough to reconstruct the instrument.
Those assumptions work until they do not. When an adjusted contract appears, sizing can be wrong, PnL can be wrong, and a backtest can select a contract that did not represent the economic exposure the strategy intended.
Application pattern
When a strategy or UI selects an option contract:
- Fetch contract reference data with the relevant
as_ofdate when history matters. - Store the full option ticker and reference fields.
- Read
shares_per_contractinstead of assuming 100. - Preserve
additional_underlyingswhen present. - Log correction fields and request id.
- Reject adjusted contracts or send them to an explicit handling branch if the strategy only supports standard contracts.
For current dashboards, display adjusted contracts with a warning or detail panel. For backtests, either model adjusted contracts explicitly or exclude them with a reject reason.
Backtesting checklist
| Check | Why it matters |
|---|---|
as_of contract lookup | Prevents selecting contracts unavailable on the research date. |
| Full option ticker | Avoids joining by underlying alone. |
| Deliverable fields | Protects sizing and PnL. |
| Split-adjustment flag on bars | Keeps price series assumptions visible. |
| Quote/trade timestamps | Confirms market evidence after the corporate action. |
| Reject reason | Documents when the engine excludes adjusted contracts. |
Official references
- OCC information memos
- OCC corporate action information submission form
- OCC equity options product specifications
Related CuteMarkets docs
- Contracts
- Option Symbols and Contract Identity
- Aggregates
- Backtesting Data Model
- Backtesting Data Quality Checklist
Corporate-action handling should be cross-checked with Option Symbols and Contract Identity, Contracts, Stock Reference, and the Stock and Options Data Join Workflow. Splits, special dividends, deliverable changes, OCC symbology, adjusted strikes, and shares-per-contract all affect historical contract matching.
Adjustment handling notes
Adjusted options deserve a separate branch in application code. A split, special dividend, merger, or spinoff can alter shares per contract, deliverables, strike interpretation, and downstream PnL. When an adjusted contract appears, store the OCC memo reference when available, the full option ticker, underlying root, shares_per_contract, additional_underlyings, correction fields, and the market-data rows used after the adjustment.
Backtests can either model adjusted contracts explicitly or reject them with a named reason. The dangerous path is pretending every contract still represents 100 shares of the current ticker. Pair this page with Stock Reference, Contracts, and Stock and Options Data Join Workflow so corporate-action state stays attached to both the underlying series and the option leg.
Additional implementation review
Review the adjusted options workflow as a sequence of named data objects, not as a single helper call. The implementation should preserve split event, deliverable change, adjusted OCC symbol, effective date, quote window, trade window, and selected contract artifact. Those fields make support tickets, CI fixtures, and replay notebooks easier to compare because every step can point to the exact request and response that created the displayed value.
The main failure mode is that a backtest can compare pre-adjustment strikes with post-adjustment quotes and create a return that never existed. Before promoting the workflow, run one concrete example through discovery, retrieval, display, logging, and error handling. Keep the resulting artifact beside the code path so future changes can prove they still use the same terminology and the same market-data assumptions.