GET
/api/v1/options/{underlying}/iv/historyStandard tier+ · 300 req/minIV history for a single (expiry, strike) tuple — ATM by default.
Historical mean IV at a fixed (expiry, strike). Omit `strike` to auto-resolve the ATM strike at the most recent snapshot. Call+put IV at the same ts are averaged to smooth smile-skew noise.
Path parameters
Segments of the URL path, validated server-side.
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| underlying | enum | required | — | BTC or ETH. BTCETH |
Query parameters
All query parameters are optional unless marked required.
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| expiry | string | required | — | Deribit `DDMMMYY` label. |
| strike | number | optional | — | Exact strike. Omit for ATM. |
| limit | number | optional | 500 | Max points (1-5000). |
Response shape
Always wrapped in the standard envelope. Nullable fields are explicitly marked — treat missing numeric data as a real data-source gap, not as an error.
data payloadtypescript
// Wrapped in the standard envelope:
// {
// data: /* shape below */,
// meta?: { total?: number; limit?: number; offset?: number; ... }
// }
{ underlying, expiry, strike, points: Array<{ ts, value }> }Example
Copy the curl, replace YOUR_KEY with a real key from your dashboard, and run.
Requestbash
curl -sS "http://localhost:3000/api/v1/options/BTC/iv/history?expiry=27JUN25&limit=200"Responsejson
{ "data": { "underlying": "BTC", "expiry": "27JUN25", "strike": 70000, "points": [] }, "meta": { "total": 0, "limit": 200 } }Next
Check the error code reference, or get an API key to try the request against your own account.