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

Market-wide volume time series

Market-wide volume time series

GET/api/p3/volume/history

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
daysintegerOptional30≤ 400Look-back window in days. Example: 30

Example request

curl -s "https://www.coinboss.com/api/p3/volume/history?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.

FieldTypeUnitDescription
successboolean—true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`.
nownumbermsServer time when the response was built.
snapshotsarray—Snapshots.
snapshots[]object—Snapshots.
snapshots[].tsnumbermsTimestamp.
snapshots[].futuresnumber—Futures market block or value.
snapshots[].spotnumber—Spot market block or value.
daily_estarray—Daily futures volume estimate built from daily perpetual candles; shows the shape of history before hourly snapshots existed.
daily_est[]object—One UTC day: `ts` and `futures_est`.
daily_est[].tsnumbermsTimestamp.
daily_est[].futures_estnumberUSDSum of close × volume over the stored daily perpetual candles of that day. One exchange only, so far below the all-exchange `snapshots[].futures`.

Generated 2026-11-11 23:01 UTC from 1 real responses.

Example response

/api/p3/volume/history?days=30 · Real response captured 2026-11-13 04:03:41 UTC. Long arrays and maps are shortened for display: daily_est had 31 items; snapshots had 720 items.

  • {
    • "success": true,
    • "now": 1794542367057,
    • "snapshots": [
      • { … 3 },
      • { … 3 }
      ],
    • "daily_est": [
      • { … 2 },
      • { … 2 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
5m
Edge micro-cache
10s
Update frequency
snapshots every 10 min, served as hourly means; API cache 300 s
Window
days (default 30, max 400); snapshots start 2026-07-03
Data sources
History of total futures and spot 24h volume from our 10-minute snapshots, plus a daily estimate from Binance candles.
Exchange coverage
futures = all collected venues; spot = third-party market-data aggregator ranked coins excluding 15 stablecoins
Pagination
none
Units
USD
Method
daily_est = SUM(close * volume) over 1d candles
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 04:03:41 UTCHTTP 2002 msSchema matchesNewest data point 64m old

Availability, last 30 days

100% of 409 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/p3/volume/historyAvailable
Parameters

integer · default 30 · max 400 — Look-back window in days.

Request URLhttps://www.coinboss.com/api/p3/volume/history?days=30
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.