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

Coin volume page data

Coin volume page data (exchange split and 30-day daily series)

GET/api/volume/coin
`daily_30d` holds one value per UTC day: the last rolling-24h snapshot recorded that day, not a calendar-day sum. The series currently spans about 8 days because the underlying table keeps 7 days.

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
symbolstringRequired——Coin symbol (upper-cased, max 30); 404 when no data. Example: BTC

Example request

curl -s "https://www.coinboss.com/api/volume/coin?symbol=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 }`.
dataobject—Payload.
data.symbolstring—Instrument symbol as normalised by CoinBoss (for example BTCUSDT).
data.total_24h_usdnumberUSDSum of 24h futures volume of the coin over the listed exchanges (the 15 largest by volume).
data.exchangesarray—Exchanges.
data.exchanges[]object—Exchanges.
data.exchanges[].exchangestring—Exchange id, lower case (for example `binance`).
data.exchanges[].volume_usdnumberUSDVolume in USD notional.
data.exchanges[].share_pctnumber%Share of the total.
data.daily_30darray—Daily volume history for the last 30 days, oldest first; one entry per UTC day.
data.daily_30d[]object—One UTC day: `volume_usd` is the rolling 24h volume snapshot taken at `as_of`, the last hourly snapshot of that day.
data.daily_30d[].datestring—Calendar date (UTC).
data.daily_30d[].volume_usdnumberUSDVolume in USD notional.
data.daily_30d[].as_ofnumbermsTime of the last sample that went into this day.
data.daily_30d_basisstring—How the daily series is built (which samples are used and where the history starts).

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

Example response

/api/volume/coin?symbol=BTC · Real response captured 2026-11-13 03:57:35 UTC. Long arrays and maps are shortened for display: data.daily_30d had 8 items; data.exchanges had 15 items.

  • {
    • "success": true,
    • "data": {
      • "symbol": "BTC",
      • "total_24h_usd": 66180849481.29,
      • "exchanges": [ … 2 ],
      • "daily_30d": [ … 2 ],
      • "daily_30d_basis": "rolling_24h_volume_snapshot_last_of_utc_day"
      }
    }

Verified samples

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

ParametersHTTPLatencyResult
symbol=ETH20018 msPass
symbol=SOL20017 msPass
symbol=ARKM20017 msPass

Checked 2026-11-13 03:57:35 UTC

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
2m
Edge micro-cache
10s
Update frequency
tickers every 1 min; snapshots hourly; in-memory cache 120 s
Window
24h by exchange; 30 daily points
Data sources
Futures 24h volume of one coin split by exchange from exchange public tickers, plus a 30-day daily series from our hourly volume snapshots.
Exchange coverage
Top 15 exchanges by volume for the coin
Pagination
none
Sorting
volume desc
Units
USD; share in percent
Method
share_pct = exchange volume / SUM(top 15 exchanges) * 100
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:57:35 UTCHTTP 20015 msSchema matchesNewest data point 4h old

Availability, last 30 days

100% of 411 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/volume/coinAvailable
Parameters

string — Coin symbol (upper-cased, max 30); 404 when no data.

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