Skip to main content
GET
/
options
/
expiry-summary
Per-expiry IV / skew / PCR / OI / GEX (with OPEX enrichment)
curl --request GET \
  --url https://api.example.com/options/expiry-summary \
  --header 'X-API-Key: <api-key>'
{
  "data": {
    "expiries": [
      {
        "expiry": "<string>",
        "is_anchor": true,
        "dte": 123,
        "atm_iv": 123,
        "skew_25d": 123,
        "put_25d_iv": 123,
        "call_25d_iv": 123,
        "pcr": 123,
        "call_oi": 123,
        "put_oi": 123,
        "total_oi": 123,
        "net_gex": 123,
        "expiry_date": "<string>",
        "notional_oi_usd": 123,
        "max_pain": {
          "strike": 123,
          "value": 123
        }
      }
    ],
    "anchor_count": 123,
    "type_counts": {
      "daily": 0,
      "weekly": 0,
      "monthly": 0,
      "quarterly": 0
    }
  },
  "meta": {
    "version": "<string>",
    "timestamp": "<string>",
    "request_id": "<string>",
    "symbol": "<string>",
    "spot_price": 123,
    "computed_at": "<string>",
    "freshness_seconds": 123,
    "source": [
      "<string>"
    ],
    "exchanges_filtered": [
      "<string>"
    ],
    "rate_limit": {},
    "extra": {}
  },
  "success": true
}

Documentation Index

Fetch the complete documentation index at: https://docs.backquant.com/llms.txt

Use this file to discover all available pages before exploring further.

One row per active expiry with ATM IV, 25Δ skew, PCR, OI, net GEX, plus OPEX enrichment (type, is_anchor, expiry_date, notional_oi_usd, max_pain).

​
See also

OPEX calendar

IV suite

Authorizations

​
X-API-Key
string
header
required

Your BackQuant API key (same key as v1)

Headers

​
X-API-Key
string | null

Query Parameters

​
symbol
enum<string>
default:BTCUSDT

Trading symbol: BTCUSDT, ETHUSDT, SOLUSDT, or HYPEUSDT.

Available options:
BTCUSDT,
ETHUSDT,
SOLUSDT,
HYPEUSDT

Response

Successful Response

​
data
ExpirySummaryData · object
required
​
meta
V2Meta · object
required

The meta block returned alongside every v2 response.

Every field after version/timestamp is optional because endpoints attach different combinations — e.g. /v2/status skips symbol, the chain endpoint sets extra.filter_hash, etc. Listing them here means SDKs get a typed accessor for each instead of a generic meta: dict.

​
success
boolean
default:true