Skip to content
Historical options SQL

U.S. Options Historical Data API (Chinese demand hub)

Query licensed U.S. equity options history with SELECT-only SQL over REST. Ideal when you need 美股期权历史数据 for research, not CSV dumps.

GSC shows 美股期权历史数据 as a high-CTR Chinese query for OptionData. This page and /historical_data/?lang=zh are the primary landing surfaces for that intent.

From Chinese search intent to SQL

Map 美股期权历史数据 demand to a concrete warehouse workflow under one OptionData key.

Authenticate

Use cus_… or apikey_… on POST https://www.optiondata.io/api/historical/sql.

Filter RawOptionTrades

Partition on date; filter symbol early. Fields include Greeks, IV, premium, OI.

Backtest rules

Replay large premium, short DTE, or custom UOA logic before going live.

Pair with live flow

Use the WebSocket for alerts; use SQL to validate thresholds historically.

Why teams search 美股期权历史数据

  • Licensed U.S. equity options history without exchange connectivity
  • SQL flexibility vs static file vendors
  • Greeks and IV on stored trades when available
  • Same key as realtime, option chain, and market structure
  • Trial row caps; full access with active/trialing realtime plan
  • Public docs: /docs/historical-option-trades-api/
Example: top AAPL premium prints today
curl -X POST 'https://www.optiondata.io/api/historical/sql' \
  -H 'Content-Type: application/json' \
  -d '{
    "api_key": "YOUR_API_KEY",
    "sql": "SELECT symbol, strike, put_call, size, price, premium FROM RawOptionTrades WHERE date = today() AND symbol = '\''AAPL'\'' ORDER BY premium DESC LIMIT 25"
  }'

U.S. options historical data FAQ

What is 美股期权历史数据 on OptionData?

It is OPRA-derived U.S. equity option trade history stored in ClickHouse and queried via POST /api/historical/sql — the same warehouse powering /historical_data/.

How far back does history go?

Coverage starts in February 2025 with 2.8B+ stored trades and growing.

Is historical data RAW or aggregated?

Historical SQL is raw trade prints (not AGGREGATED mode). Aggregate in SQL with GROUP BY when needed.

How should Hong Kong / overseas Chinese users start?

Use https://www.optiondata.io/historical_data/?lang=zh or this hub page; Chinese landing pages are already pickable in Google Search Console for HK and related markets.