24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/options/iv-history
GETAvailable

Options implied-volatility history

Options implied-volatility history

GET/api/options/iv-history
Single venue: computed from Deribit public option data only. `volume_usd`-type fields are premium-based where the venue reports premium turnover. For six venues with per-venue coverage use `/api/sd/options/overview`. One point per day.

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
currencystringOptionalBTCBTC, ETHUnderlying: `BTC` or `ETH`. Any other value returns 400 `INVALID_PARAM`. Alias: `coin`. Example: BTC

Example request

curl -s "https://www.coinboss.com/api/options/iv-history?currency=BTC"

Response fields

The field table is generated from real responses, so it lists exactly what the endpoint returns. Paths use a[] for array items and {*} for objects keyed by a dynamic name such as a coin or an exchange.

FieldTypeUnitDescription
successboolean—true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`.
currencystring—Currency / asset symbol.
countnumber—Number of items.
updated_atnumbermsWhen this row was last updated.
rowsarray—Result rows.
rows[]object—Result rows.
rows[].datestring—Calendar date (UTC).
rows[].atm_iv_30dnumber%Constant 30-day at-the-money implied volatility, linearly interpolated between the two expiries around 30 days; one snapshot per UTC day (annualised, 37.5 = 37.5 %).
rows[].index_pricenumber—Index price of the underlying.

Generated 2026-11-11 23:00 UTC from 2 real responses.

Example response

/api/options/iv-history?currency=BTC · Real response captured 2026-11-13 03:58:24 UTC. Long arrays and maps are shortened for display: rows had 132 items.

  • {
    • "success": true,
    • "currency": "BTC",
    • "count": 132,
    • "updated_at": 1794529604144,
    • "rows": [
      • { … 3 },
      • { … 3 }
      ]
    }

Verified samples

Besides the example above, the probe calls this endpoint with these parameters and checks the schema each time.

ParametersHTTPLatencyResult
currency=ETH2001 msPass
currency=SOL4001 msPass returns the expected error

Checked 2026-11-13 03:58:24 UTC

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
10m
Edge micro-cache
10s
Update frequency
one point per UTC day (checked every 30 min; today's point written once per process per day)
Window
all daily points accumulated since the feature launched
Data sources
Daily 30-day at-the-money implied volatility, derived in-house from a single exchange's options data (Deribit).
Exchange coverage
BTC and ETH; history only exists from the date local accumulation started (no backfill).
Sorting
date ascending
Units
percent (annualized implied volatility); USD (index price)
Method
30-day ATM IV = linear interpolation by days-to-expiry between the ATM IVs of the two expiries surrounding 30 days.
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:58:24 UTCHTTP 2001 msSchema matchesNewest data point 3.5h old

Availability, last 30 days

100% of 410 checks passed

Errors

Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →

CodeHTTPMeaningWhat to do
INVALID_PARAM400A required parameter is missing or a value is not accepted. `param` names the parameter when it is known.Do not retry unchanged; fix the request.
UNAUTHORIZED401The `CB-API-KEY` header was sent but the key is unknown or revoked. Public data needs no key — drop the header or use a valid key.Do not retry unchanged.
FORBIDDEN403The route is not part of the public API (internal or account-only).Do not retry.
NOT_FOUND404Unknown route, or the requested coin / exchange / fund does not exist.Do not retry; check the path and identifiers against the catalog.
RATE_LIMITED429More requests than the per-minute limit. `Retry-After` gives the seconds to wait.Wait for `Retry-After`, then retry with backoff.
INTERNAL500Unexpected server error. The message is generic by design; quote `request_id` when reporting it.Retry once after a few seconds; report it with the request id if it persists.
UPSTREAM_FAILED503The data source behind this endpoint did not answer in time. No stale or substitute numbers are returned in its place.Retry with backoff; check the status page.
UNAVAILABLE501 / 503The dataset is temporarily not ready (cache warming) or the endpoint has no lawful public source yet.Retry later; the catalog marks endpoints that are unavailable by design.
REQUEST_FAILED200Some older endpoints answer HTTP 200 with `success: false`. Always check `success`, not only the HTTP status.Depends on the message; treat as a failed request.

Try it

GET/api/options/iv-historyAvailable
Parameters

string · default BTC — Underlying: `BTC` or `ETH`. Any other value returns 400 `INVALID_PARAM`. Alias: `coin`.

Request URLhttps://www.coinboss.com/api/options/iv-history?currency=BTC
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.