Volatility history for one coin
Volatility history for one coin
/api/p3/volatility/seriesRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| coin | string | Optional | BTC | — | Base coin symbol (uppercase, e.g. BTC). Example: BTC |
| days | integer | Optional | 30 | ≤ 700 | Look-back window in days. Example: 30 |
Example request
curl -s "https://www.coinboss.com/api/p3/volatility/series?coin=BTC&days=30"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.
| Field | Type | Unit | Description |
|---|---|---|---|
| success | boolean | — | true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`. |
| coin | string | — | Coin symbol, upper case (for example BTC). |
| series | array | — | Time series. |
| series[] | object | — | Time series. |
| series[].ts | number | ms | Timestamp. |
| series[].vol_pct | number | % | Intraday range of that day's daily candle: (high − low) ÷ open × 100. |
Generated 2026-11-11 23:00 UTC from 4 real responses.
Example response
/api/p3/volatility/series?coin=BTC&days=30 · Real response captured 2026-11-13 04:02:31 UTC. Long arrays and maps are shortened for display: series had 31 items.
- "success"true
- "coin""BTC"
- "series"
Verified samples
Besides the example above, the probe calls this endpoint with these parameters and checks the schema each time.
| Parameters | HTTP | Latency | Result |
|---|---|---|---|
| coin=ETH&days=30 | 200 | 7 ms | Pass |
| coin=SOL&days=30 | 200 | 7 ms | Pass |
| coin=ARKM&days=30 | 200 | 7 ms | Pass |
Checked 2026-11-13 03:57:34 UTC
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 10m
- Edge micro-cache
- 10s
- Update frequency
- daily bars; recomputed on request (10 min cache)
- Window
- last 30 days by default (`days` max 700)
- Data sources
- Daily price range series computed in-house from exchange USDT-perpetual daily klines.
- Exchange coverage
- Any coin with daily klines (default BTC).
- Sorting
- date ascending
- Units
- percent
- Method
- Daily range = (high - low) / open x 100.
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
Availability, last 30 days
100% of 412 checks passed
Errors
Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →
| Code | HTTP | Meaning | What to do |
|---|---|---|---|
| INVALID_PARAM | 400 | A 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. |
| UNAUTHORIZED | 401 | The `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. |
| FORBIDDEN | 403 | The route is not part of the public API (internal or account-only). | Do not retry. |
| NOT_FOUND | 404 | Unknown route, or the requested coin / exchange / fund does not exist. | Do not retry; check the path and identifiers against the catalog. |
| RATE_LIMITED | 429 | More requests than the per-minute limit. `Retry-After` gives the seconds to wait. | Wait for `Retry-After`, then retry with backoff. |
| INTERNAL | 500 | Unexpected 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_FAILED | 503 | The 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. |
| UNAVAILABLE | 501 / 503 | The 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_FAILED | 200 | Some 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
/api/p3/volatility/seriesAvailablestring · default BTC — Base coin symbol (uppercase, e.g. BTC).
integer · default 30 · max 700 — Look-back window in days.
https://www.coinboss.com/api/p3/volatility/series?coin=BTC&days=30More in this category
- Coin heatmap data /api/coin-heatmap
- Full coin list /api/coins/all
- Coin search /api/coins/search
- Coin-page exchange table /api/currency/ex-table
- Coin money flow /api/currency/flows
- Coin list for navigation /api/currency/list
- Per-exchange markets for one coin /api/currency/markets
- Coin detail overview /api/currency/overview
- Coin price performance across periods /api/currency/performance
- Spot taker net inflow for one coin /api/currency/spot-netflow
- Margin borrow-rate matrix /api/margin-fee/matrix
- Margin borrow rates /api/margin/rates
- Gainers & losers (with volume floor) /api/market/gainers-losers
- Quick movers snapshot for top market-cap coins /api/market/top-movers
- Monthly / quarterly / yearly return matrix /api/p3/btc-returns
- Daily return matrix /api/p3/btc-returns-daily
- Weekly return matrix /api/p3/btc-returns-weekly
- Gainers & losers (futures or spot) /api/p3/gainers-losers
- Hourly candles /api/p3/klines
- Volatility overview /api/p3/volatility
- Volatility history for one coin /api/p3/volatility/series
- Spot coin market list /api/spot/coins
- Coin volume page data /api/volume/coin