GET
/api/v1/options/{underlying}/ivStandard tier+ · 300 req/minPer-strike IV at the latest snapshot for a single expiry.
Resolves `expiry` to a concrete chain slice (nearest upcoming expiry if omitted). Calls and puts are distinct rows so clients can plot smile curves side-by-side.
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 | optional | — | Deribit `DDMMMYY`. Defaults to nearest upcoming live expiry. |
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, points: Array<{ expiry, strike, optionType, markIv }> }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"Responsejson
{ "data": { "underlying": "BTC", "expiry": "25APR25", "points": [] }, "meta": { "total": 0 } }Next
Check the error code reference, or get an API key to try the request against your own account.