SPY Options Expiration Dates 2026
A SPY-focused 2026 expiration reference for common weekly and monthly workflows: January 9 weekly options, May historical dates, the current June 18 OpEx handoff, and the API workflow for confirming listed SPY contracts.
January 9, 2026
Friday weekly cycle
This is a Friday weekly-cycle date. Confirm listed contracts before requesting chains.
May 2026 monthly OpEx
Friday, May 15, 2026
The May standard monthly SPY expiration is the third Friday.
June 2026 monthly OpEx
Thursday, June 18, 2026
The monthly cycle moves because Friday, June 19 is Juneteenth.
SPY workflow
Use the calendar to classify, not to invent contracts
SPY is liquid enough that weekly expiration workflows are common, but a reliable implementation should still begin with listed dates. The calendar tells you whether January 9, April 17, or May 15 belongs to a weekly, monthly, or quarterly cycle. The API tells you which SPY contracts are actually listed for that date, which strikes exist, and which OCC tickers should be used in downstream quote, trade, or aggregate requests.
This distinction is especially important for backtests. If a model assumes a date exists and later joins bars, quotes, or snapshots to that assumption, it can create silent survivorship or empty-chain errors. A cleaner implementation fetches expirations, tags each date, requests contracts for the selected date, and stores the full contract ticker with every measurement.
January 2026 SPY weekly and monthly reference
January 9 is a useful weekly-cycle example, so the month is broken out directly.
| Date | Cycle | Note |
|---|---|---|
| Friday, January 2, 2026 | Weekly | Weekly Friday cycle |
| Friday, January 9, 2026 | Weekly | Friday weekly expiration reference. |
| Friday, January 16, 2026 | Monthly | Standard monthly OpEx |
| Friday, January 23, 2026 | Weekly | Weekly Friday cycle |
| Friday, January 30, 2026 | Weekly | Weekly Friday cycle |
April, May, and June 2026 SPY expiration dates
April and May are now historical context. June 18 is the current standard monthly and quarterly SPY OpEx anchor after the May cycle.
| Date | Cycle | Note |
|---|---|---|
| Thursday, April 2, 2026 | Weekly | Moved from April 3, 2026 for a market holiday. |
| Friday, April 10, 2026 | Weekly | Weekly Friday cycle |
| Friday, April 17, 2026 | Monthly | Standard monthly OpEx |
| Friday, April 24, 2026 | Weekly | Weekly Friday cycle |
| Friday, May 1, 2026 | Weekly | Weekly Friday cycle |
| Friday, May 8, 2026 | Weekly | Weekly Friday cycle |
| Friday, May 15, 2026 | Monthly | Standard monthly OpEx |
| Friday, May 22, 2026 | Weekly | Weekly Friday cycle |
| Friday, May 29, 2026 | Weekly | Weekly Friday cycle |
| Friday, June 5, 2026 | Weekly | Weekly Friday cycle |
| Friday, June 12, 2026 | Weekly | Weekly Friday cycle |
| Thursday, June 18, 2026 | Quarterly | Moved from June 19, 2026 for a market holiday. |
| Friday, June 26, 2026 | Weekly | Weekly Friday cycle |
API example
Fetch SPY listed dates before building the chain
curl "https://api.cutemarkets.com/v1/tickers/expirations/SPY/" \
-H "Authorization: Bearer YOUR_API_KEY"
curl "https://api.cutemarkets.com/v1/options/contracts/?underlying_ticker=SPY&expiration_date=2026-01-09&limit=100" \
-H "Authorization: Bearer YOUR_API_KEY"Last verified
Date-sensitive calendar references on this page were checked on May 30, 2026. Calendar math is useful for planning, but listed contracts and exchange calendars should still be verified before production workflows run.
SPY options expiration FAQ
Was January 9, 2026 a SPY options expiration date?
January 9, 2026 was a Friday weekly-cycle date. Use listed-expiration data to confirm the actual SPY contracts available for that date.
When is the May 2026 SPY monthly expiration?
The standard May 2026 monthly SPY options expiration is Friday, May 15, 2026.
Should SPY weekly dates be hard-coded?
No. A static calendar is useful for planning, but production tools should fetch listed SPY expirations before requesting chains or contracts.
Operational usage
How to use SPY Options Expiration Dates 2026 in a real workflow
Treat this page as a decision boundary for the surrounding API workflow. Before a value from SPY Options Expiration Dates 2026enters a scanner, dashboard, calendar, backtest, or support answer, store the source route, request parameters, relevant timestamp, freshness label, and the reason the value is suitable for the next step.
The important implementation habit is to keep display labels separate from stable identifiers. Dates should remain tied to the calendar rule or listed-expiration source that produced them. Option rows should keep the OCC symbol, expiration, strike, side, quote state, and pagination context that created the row. Provider or product answers should keep the entitlement, licensing, and support assumptions visible.
When the workflow changes, rerun the page against one concrete example instead of trusting a general claim. Pick the ticker, date window, endpoint family, and expected output artifact. Then verify that the same terminology appears in the API request, UI label, log entry, and review checklist.
Related pages
Expiration calendar
Compare SPY against the broader weekly, monthly, and holiday-adjusted calendar.
2026 options expiration dates
Use the primary monthly and quarterly OpEx reference for 2026.
Expiration date filters
Filter contracts by exact SPY expiration or a bounded expiration window.
Expirations docs
Fetch listed SPY expiration dates before requesting chains or contracts.