Weekly date
January 9, 2026 belongs to the weekly SPY expiration workflow.
Ticker-Specific Expiration Questions
SPY January 9 2026 Options Expiration
A direct answer for the high-impression query around SPY January 9, 2026 weekly options, followed by the January monthly context.
Quick answerLast verified May 7, 2026
January 9, 2026 was a Friday weekly SPY options expiration date, not the standard January monthly expiration. The standard January 2026 monthly cycle was Friday, January 16, 2026. For production use, fetch listed SPY expirations before assuming a date exists.
Date
January 9, 2026
Friday weekly cycle for SPY workflows.
Monthly cycle
January 16, 2026
Standard January 2026 monthly OpEx.
Ticker
SPY
Highly active ETF options with weekly expiration demand.
Weekly versus monthly SPY expiration
The confusion comes from treating every SPY Friday as monthly OpEx. January 9 was a Friday weekly date; January 16 was the third-Friday monthly cycle.
A chain viewer should display both, but label them differently. Weekly and monthly cycles can behave differently around open interest, spreads, and dealer positioning.
Why the label matters for backtests and scanners
A SPY backtest that pools January 9 with the January monthly cycle can hide differences in liquidity, open interest concentration, and contract availability. Weekly contracts are useful, but they are not interchangeable with the standard monthly cycle.
The safer workflow is to fetch listed SPY expirations, classify January 9 as weekly, classify January 16 as monthly, and preserve the full OCC ticker when joining quotes, trades, aggregates, or snapshots.
Monthly date
January 16, 2026 is the standard January monthly OpEx date.
Data rule
Listed SPY expirations should drive contract requests, not generated Fridays alone.
SPY January 2026 date context
| Date | Cycle | Interpretation |
|---|---|---|
| January 2, 2026 | Weekly | First Friday weekly date after New Year. |
| January 9, 2026 | Weekly | The queried SPY weekly expiration date. |
| January 16, 2026 | Monthly | Standard January 2026 monthly OpEx. |
| January 23, 2026 | Weekly | Weekly cycle after monthly OpEx. |
| January 30, 2026 | Weekly | Weekly cycle near month-end. |
API example
Verify the answer with listed data
spy expirations
curl "https://api.cutemarkets.com/v1/tickers/expirations/SPY/" \
-H "Authorization: Bearer YOUR_API_KEY"How to implement
Implementation checklist
01
Fetch SPY expirations
Start with the listed expiration endpoint so the workflow is tied to actual SPY contracts.
02
Classify January 9
Mark January 9, 2026 as a weekly date and January 16, 2026 as the monthly date.
03
Request contracts by date
Only after classification, request contracts or chains for the selected SPY expiration.
Last verified
This guide was last reviewed on May 7, 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
Was January 9, 2026 the January monthly SPY expiration?
No. It was a weekly Friday date. The standard monthly January 2026 date was January 16.
Why does SPY have so many expiration dates?
SPY is a highly active ETF options product, so weekly expiration workflows are common.
Should I hard-code SPY Fridays?
No. Fetch listed SPY expirations and classify the dates after discovery.
Related pages
Options Q&A hub
Browse exact-answer pages for expirations, OCC symbols, options data, and provider comparisons.
May OpEx 2026
Use the exact May 15, 2026 monthly OpEx answer before ticker-level validation.
Expiration data workflow
Separate calendar planning from listed-expiration validation before requesting market data.
Expiration calendar
Use the interactive calendar for weekly, monthly, quarterly, and holiday-adjusted dates.
Expiration API
Fetch listed expiration dates from the API instead of hard-coding calendar rules.
Expirations docs
Review the endpoint used to discover listed option expiration dates.