Options Data API
for chains, Greeks, and backtests.

Build scanners, dashboards, and backtests with live chains, Greeks, quotes, trades, OHLC bars, and historical contracts for every U.S.-listed option. Structured JSON. Consistent format. Ready to use in minutes.

Create API keyFree

View docs Explore cutebacktests

100%Coverage10+years history18+REST endpoints4indicators

German precision & billing

CuteMarkets is proudly headquartered and engineered in Germany. We apply the famous German benchmark for precision directly to our trading data, guaranteeing rigorous quality control and maximum uptime.

For B2B customers, our European entity ensures 100% compliant and hassle-free accounting. Every subscription automatically generates proper German billing formats and fully compliant EU tax invoices (with reverse charge and VAT handling natively built in).

Try it yourself

Build a request. See the response.

Pick a ticker, expiration, and contract type. Then hit Send to see exactly what our API returns.

Underlying Ticker

Contract Type

Expiration Date

Results Limit

Create Account

Request

GEThttps://api.cutemarkets.com/v1/options/chain/AAPL?expiration_date=2026-05-01&contract_type=call&limit=5

Authorization:Bearer YOUR_API_KEY

Response

Configure your request above and hit Send

Available endpoints

GET/v1/options/chain/{ticker}

Full options chain snapshot

GET/v1/options/snapshot/{underlying}/{contract}

Single option contract snapshot

GET/v1/options/contracts/{ticker}

Single contract with Greeks & IV

GET/v1/options/quotes/{ticker}

Historical NBBO quotes (nanosecond)

GET/v1/options/trades/{ticker}

Trade-level tick data

GET/v1/options/aggs/{ticker}/prev

Previous trading day OHLC bar

GET/v1/options/aggs/{ticker}/{span}

OHLCV aggregated bars

GET/v1/options/open-close/{ticker}/{date}

Daily OHLC + pre/post market

GET/v1/options/indicators/sma/{ticker}

Technical indicators (SMA, EMA, RSI…)

About CuteMarkets

Built by traders,
for developers.

CuteMarkets was founded after years of building and running options strategies with the same pain: expensive data, legacy APIs, and too much integration friction. We built the API we wanted to use ourselves: clean, consistent, and production-ready.

Read our story