OCC Symbols And Parsing

Why Do OCC Option Symbols Have Spaces?

Why symbols like SPY 260515C00500000 can contain spaces before the date block.

Quick answerLast verified April 28, 2026

OCC-style option symbols can show spaces because the root field is fixed-width and can be padded to six characters. Compact displays often remove those spaces. A robust parser should accept both padded and compact forms and normalize them to the same contract identity.

Reason

Root padding

The root field can be padded in fixed-width representations.

Compact form

No spaces

Many APIs and UIs display compact OCC tickers.

Parser rule

Accept both

Normalize before lookup or storage.

Why spaces are not part of the economic contract

Spaces are a display and parsing concern. They help fixed-width symbol formats keep the root field separate from expiration, type, and strike fields.

When building a parser, trim the root for internal storage but do not lose the ability to read padded examples from files, broker exports, or documentation.

Padded versus compact examples

FormExampleInterpretation
PaddedSPY 260515C00500000SPY May 15 2026 500 call.
CompactSPY260515C00500000Same contract identity in compact form.
API styleO:SPY260515C00500000CuteMarkets contract ticker style with option prefix.

Last verified

This Q&A page was last reviewed on April 28, 2026. Date-sensitive market calendars, provider docs, and listed contracts can change, so production workflows should verify the live source before trading or publishing an automated answer.

Related questions

Should spaces be stored?

Usually no. Store a normalized compact identifier, but accept padded input.

Can adjusted roots be longer or unusual?

Adjusted option roots can be more complex, so parsers should avoid overly narrow root assumptions.

Do spaces change the strike?

No. The strike is the final eight-digit field and is independent of root padding.

Related pages