ETF Options Data API for ETF chains, expirations, quotes, trades, and Greeks
Use CuteMarkets to build ETF options workflows around liquid U.S.-listed ETF options such as SPY, QQQ, IWM, and TLT: live chain snapshots, listed expirations, contract snapshots, quote/trade context, Greeks, and open interest from one API surface.
Evidence path
ETF option chains
Pull ETF calls and puts by expiration and inspect strikes, moneyness, Greeks, IV, and open interest together.
Expiration-aware requests
Fetch listed ETF expiration dates before requesting chains or contracts so scanners do not depend on hard-coded calendars.
Quote and trade context
Use bid/ask and trade history for liquidity checks instead of treating every ETF contract as equally tradable.
Single-contract snapshots
Inspect one contract with break-even, day stats, Greeks, latest quote, latest trade, and underlying context.
ETF workflow map
Choose the right ETF options workflow
ETF options workflows start broad, then narrow to a concrete underlying. Use this hub to choose the ETF universe, confirm whether the job needs holdings data or listed option contracts, and then move into SPY, QQQ, IWM, or TLT implementation paths only when the underlying-specific behavior matters.
| Factor | Page-specific guidance | API implementation |
|---|---|---|
| Universe selection | Start broad when the question is "ETF options data" and the user has not chosen the exposure yet. | Fetch expirations and chains only after the application chooses a concrete underlying such as SPY, QQQ, IWM, or TLT. |
| Holdings distinction | ETF holdings, constituents, and fund weights are a different dataset from ETF option contracts. | Keep holdings providers separate; use CuteMarkets for option chains, quotes, trades, Greeks, OI, and expirations. |
| Reusable scanner model | The common model is expiration discovery, chain filtering, quote-quality checks, and single-contract drilldown. | Store the underlying ticker, expiration date, OCC symbol, quote timestamp, and spread metrics together. |
| Ticker handoff | This hub points readers to the specific ETF workflow instead of treating every ETF as interchangeable. | Use SPY, QQQ, IWM, and TLT as distinct workflow paths with ticker-specific examples. |
ETF hub
ETF options are a workflow family
An ETF options hub should separate the fund question from the options question. Holdings, constituents, weight files, creations, redemptions, and fund metadata are not the same dataset as listed option contracts, chain snapshots, contract snapshots, quotes, trades, Greeks, IV, open interest, and expirations.
Use the hub to choose the underlying first. A high-liquidity SPY workflow, a QQQ weekly scanner, an IWM small-cap liquidity check, and a TLT rates-event replay should share the same endpoint grammar while keeping different rejection rules.
ETF decision table
Pick the ETF workflow before requesting a chain
| Underlying | Primary question | Extra check |
|---|---|---|
| SPY | Broad index exposure, dense expiration calendar, liquid chain review | Do not confuse SPY ETF options with SPX or SPXW index options. |
| QQQ | Nasdaq-100 exposure, weekly scans, technology-heavy intraday risk | Keep chain, quote, and underlying timestamps separate on short-dated rows. |
| IWM | Small-cap beta, breadth-sensitive screens, liquidity filtering | Use stricter spread, size, and quote-age rejects. |
| TLT | Rates-duration exposure and macro event replay | Anchor the workflow to CPI, FOMC, payrolls, auction, or rate-shock timestamps. |
Why teams use it
What ETF options workflows usually need
ETF option chains
Pull ETF calls and puts by expiration and inspect strikes, moneyness, Greeks, IV, and open interest together.
Expiration-aware requests
Fetch listed ETF expiration dates before requesting chains or contracts so scanners do not depend on hard-coded calendars.
Quote and trade context
Use bid/ask and trade history for liquidity checks instead of treating every ETF contract as equally tradable.
Single-contract snapshots
Inspect one contract with break-even, day stats, Greeks, latest quote, latest trade, and underlying context.
Historical research path
Pair contract discovery with historical quote, trade, and aggregate data for more realistic ETF options backtests.
Not ETF holdings data
This guide covers ETF options market data, not ETF constituent or holdings files.
Use cases
What you can build with this options data API
ETF chain explorers
Build a focused ETF option chain view with expiration filters, open interest sorting, and Greeks columns.
Open how-toETF scanners
Rank contracts by liquidity, spread, IV, delta, and expiration concentration, open interest, and quote quality.
Open how-toBacktesting and research
Reconstruct historical ETF option setups with contract, quote, trade, and aggregate context.
Open how-toRisk dashboards
Show ETF exposure, option sensitivity, and expiry concentration inside internal tools.
Open how-toDeveloper examples
Two code paths teams usually need first
Request 01
etf chain
curl "https://api.cutemarkets.com/v1/options/chain/SPY/?expiration_date=2026-05-15&limit=25" \
-H "Authorization: Bearer YOUR_API_KEY"Request 02
etf expirations
curl "https://api.cutemarkets.com/v1/tickers/expirations/SPY/" \
-H "Authorization: Bearer YOUR_API_KEY"Evaluate and compare
Why chain snapshots alone are not enough
ETF options workflows are usually ticker-specific. Compare the hub and the high-volume ETF pages together so internal scanners, dashboards, and research jobs can reuse the same chain, quote, trade, Greeks, open-interest, and expiration patterns across underlyings.
Options Data API Evaluation Framework
Use a workflow-first framework before comparing providers, endpoints, and pricing.
Options Expiration Data Workflow
Separate calendar planning from listed-expiration validation before requesting chains or contracts.
SPY Options Data API
Build SPY chain, expiration, quote, trade, Greeks, and open-interest workflows.
QQQ Options Data API
Build QQQ options scanners and research flows for Nasdaq-100 ETF contracts.
IWM Options Data API
Analyze Russell 2000 ETF options with chains, quotes, trades, Greeks, and expirations.
TLT Options Data API
Inspect long-duration Treasury ETF options with chain, quote, trade, and OI context.
Open next
Docs and research for the next step
Docs to open next
Relevant API docs
Tutorials and research
Related articles
FAQ
Common questions about this options data API
Does CuteMarkets provide ETF holdings data?
No. This ETF page is about ETF options market data: chains, expirations, contracts, quotes, trades, Greeks, snapshots, and open interest. It is not a fund-holdings or ETF constituents API.
Does CuteMarkets provide both real-time and historical options data?
Yes. CuteMarkets supports real-time snapshots and historical workflows across contracts, trades, quotes, aggregates, and expirations, with plan-specific live or delayed access.
Do you provide quotes, trades, and historical contracts?
Yes. The platform includes contracts, chain snapshots, contract snapshots, trade history, quote history, aggregates, and expiration lookups for U.S.-listed options.
Do you provide the earnings calendar too?
CuteMarkets provides the options data layer. Earnings timing should come from a dedicated earnings calendar source that you combine with the options data.
Build ETF options workflows without a separate holdings project
Start from ETF expirations and chain data, then add quotes, trades, snapshots, and historical context as the workflow becomes more execution-aware.