GETAvailable
Per-exchange volume-share history
Per-exchange volume-share history
GET
/api/p3/volume/exchange-historyRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| days | integer | Optional | 30 | ≤ 400 | Look-back window in days. Example: 30 |
Example request
curl -s "https://www.coinboss.com/api/p3/volume/exchange-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.
| Field | Type | Unit | Description |
|---|---|---|---|
| success | boolean | — | true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`. |
| snapshots | array | — | Snapshots. |
| snapshots[] | object | — | Snapshots. |
| snapshots[].ts | number | ms | Timestamp. |
| snapshots[].exchanges | array | — | Exchanges. |
| snapshots[].exchanges[] | object | — | Exchanges. |
| snapshots[].exchanges[].ex | string | — | Exchange id, lower case. |
| snapshots[].exchanges[].v | number | — | Value. |
Generated 2026-11-11 23:00 UTC from 1 real responses.
Example response
/api/p3/volume/exchange-history?days=30 · Real response captured 2026-11-13 04:02:50 UTC. Long arrays and maps are shortened for display: snapshots had 720 items; snapshots[].exchanges had 27 items.
- "success"true
- "snapshots"
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, last snapshot of each hour served; API cache 300 s
- Window
- days (default 30, max 400)
- Data sources
- Per-exchange futures 24h volume history from our 10-minute snapshots of exchange tickers.
- Exchange coverage
- All collected derivatives venues
- Pagination
- none
- Units
- USD
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
AvailableChecked 2026-11-13 04:02:50 UTCHTTP 2003 msSchema matchesNewest data point 13m 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 →
| 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
GET
/api/p3/volume/exchange-historyAvailableParameters
integer · default 30 · max 400 — Look-back window in days.
Request URL
https://www.coinboss.com/api/p3/volume/exchange-history?days=30Choose an endpoint and press “Send request”. The response, headers and timing will appear here.
More in this category
- Exchange on-chain balances for one coin /api/exchange-balances
- Exchange balance detail /api/exchange-balances/exchange-detail
- On-chain balances per coin for one exchange /api/exchange-balances/exchange/:ex
- Exchanges with on-chain balance data /api/exchange-balances/exchanges-list
- Exchange balance history /api/exchange-balances/history
- Exchange balance list /api/exchange-balances/list
- Symbols supported by exchange balances /api/exchange-balances/symbols
- Derivatives overview for one exchange /api/exchanges/detail
- Derivatives market list for one exchange /api/exchanges/markets
- Top movers within one exchange /api/exchanges/movers
- Open-interest history for one exchange /api/exchanges/oi-history
- Derivatives exchange ranking /api/exchanges/ranking
- Homepage exchange BTC balance summary /api/home/exchange-btc-balances
- Per-exchange volume-share history /api/p3/volume/exchange-history
- Exchange reserves history /api/reserves/history
- Exchange reserves overview /api/reserves/overview
- Exchange asset transparency /api/transparency
- Exchange share of BTC volume /api/volume/btc-ex-share
- Exchange share of one coin's volume /api/volume/coin-ex-share
- Exchange share of spot volume /api/volume/spot-ex-share
- US vs offshore exchange volume /api/volume/us-vs-offshore