Options API endpoint coverage matrix
Map a real options-data workflow to the CuteMarkets endpoints it needs before you write a wrapper, model a request budget, or compare providers. The useful answer is not whether an API has “options data”; it is whether the endpoint surface covers the objects your product must reproduce.
Selected workflow
Backtesting
5 core endpoint groups are marked as required or commonly useful for this workflow.
| Object | Endpoint | Coverage | Docs |
|---|---|---|---|
| Chains | GET /v1/options/chain/{ticker} | Calls and puts by expiration with Greeks, IV, OI, latest quote, latest trade, and underlying context. | Open |
| Contracts | GET /v1/options/contracts | Contract discovery by underlying, expiration, strike, type, OCC symbol, and historical as_of date. | Open |
| Quotes | GET /v1/options/quotes/{option_ticker} | Historical bid and ask prices, sizes, exchanges, sequence fields, and timestamp filters. | Open |
| Trades | GET /v1/options/trades/{option_ticker} | Tick-level prints with price, size, exchange, conditions, and nanosecond timestamps. | Open |
| Snapshots | GET /v1/options/snapshot/{ticker}/{option_ticker} | One-contract drilldowns with break-even, day stats, Greeks, IV, OI, quote, trade, and underlying data. | Open |
| Expirations | GET /v1/tickers/expirations/{ticker} | Listed expiration dates for the selected underlying before chain or contract requests. | Open |
| Aggregates | GET /v1/options/aggs/{option_ticker}/range | Historical OHLC bars, VWAP, volume, and open/close context for option contracts. | Open |
| Indicators | GET /v1/indicators/{type}/{ticker} | Server-side SMA, EMA, MACD, and RSI for broader charting and watchlist workflows. | Open |
Backtesting needs objects in order
Start with historical contracts and expirations, then fetch quotes, trades, aggregates, or snapshots only for selected legs.
0DTE needs freshness checks
Same-day chains are useful only when quote timing, spread, size, and selected-contract details stay visible.
Python wrappers should stay small
Map the endpoint sequence first, then turn only the used calls into a Python helper or internal SDK.
Buyer use case
Use coverage to remove vague vendor comparisons
A practical options-data evaluation should list the exact objects required by the workflow: contracts, expirations, chains, quotes, trades, snapshots, Greeks, open interest, aggregates, and indicators. This matrix gives that checklist a concrete shape before you compare docs, pricing, and implementation effort.