Read this page with OCC Option Symbol Format, Contracts, Options Contract Selection, Corporate Actions and Adjusted Options, and Historical Options Data API.
Option symbols are compact identifiers for very specific instruments. A single underlying can have thousands of listed contracts across expirations, strikes, call and put sides, weekly cycles, adjusted deliverables, and expired series.
Use this guide to explain OCC-style option symbols, CuteMarkets option tickers, and why contract reference data belongs beside quotes, trades, bars, and backtest fills.
Quick answer
An options contract is identified by underlying root, expiration date, call or put type, and strike price. CuteMarkets uses full contract tickers such as O:NFLX260402C00100000, where O: marks an option ticker and the remaining body follows the common OCC-style compact pattern. Do not infer all contract details from a string alone when reference data is available.
Reading the ticker
Example:
O:NFLX260402C00100000
| Segment | Meaning |
|---|---|
O: | CuteMarkets option ticker prefix. |
NFLX | Underlying root. |
260402 | Expiration date, YYMMDD, meaning 2026-04-02. |
C | Contract type, call. P means put. |
00100000 | Strike price scaled by 1000, meaning 100.000. |
The compact symbol is useful for lookups and joins, but the contract reference response is the safer source for application logic. It can include expiration, strike, contract type, exercise style, shares per contract, primary exchange, correction fields, and adjusted deliverables.
Identity is more than text parsing
Parsing the symbol can answer basic questions. Reference data answers whether that instrument existed for the date you care about, what deliverable it represented, and whether corporate actions changed the standard contract assumptions.
| Need | Use |
|---|---|
| Decode a known ticker for display | Symbol parser plus contract detail. |
| Build a historical universe | Contracts endpoint with as_of. |
| Validate a user-supplied contract | Contract detail endpoint. |
| Backtest option selection | Contracts first, then quotes or trades for selected contracts. |
| Handle splits and mergers | Contract detail fields such as shares_per_contract and additional_underlyings. |
Common mistakes
The first mistake is building old backtests from today's option chain. A contract universe changes through time. Weekly series are listed and delisted, expirations pass, strikes appear as the underlying moves, and adjusted contracts can remain after corporate actions. Use point-in-time contract discovery when the research date matters.
The second mistake is treating every contract as a standard 100-share equity option. Many are, but adjusted contracts can represent different deliverables. A sizing engine should read shares_per_contract and adjustment metadata instead of hard-coding 100 everywhere.
The third mistake is joining option data only by underlying ticker. NFLX is not enough. Store the full option ticker with every quote, trade, aggregate bar, snapshot, and simulated fill.
Storage checklist
For every contract selected by a system, store:
- Full option ticker.
- Underlying ticker.
- Expiration date.
- Contract type.
- Strike price.
- Selection timestamp or
as_ofdate. - Reference response or reference version fields used by the strategy.
- Shares per contract and any additional deliverables.
- Endpoint and request id used to select the contract.
Official references
Related CuteMarkets docs
- Contracts
- Option Chain
- Expirations
- Corporate Actions and Adjusted Options
- Backtesting Data Quality Checklist
Contract identity should be validated with Contracts, Expirations, and Corporate Actions and Adjusted Options.
Identity implementation notes
An OCC-style symbol is a compact key, not the whole instrument record. Parse it for display, then confirm the contract through Contracts or a snapshot before using it in sizing, risk, or backtesting. Store root, expiration, strike, contract type, full ticker, as_of date, shares per contract, and adjustment fields together.
This discipline matters most when a workflow crosses pages. A scanner can send a selected OCC ticker into Quotes, Trades, Aggregates, a paper order, or an alert detail. If each surface preserves the same contract identity, support can trace a row from discovery to fill evidence without guessing which strike or expiration the UI meant.
Additional implementation review
Review the option symbol parsing workflow as a sequence of named data objects, not as a single helper call. The implementation should preserve OCC root, expiration, strike, side, compact symbol, display symbol, corporate-action flag, and listed-contract lookup. 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 code can parse a readable symbol but still attach quotes, trades, or paper orders to the wrong listed contract. 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.