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

US vs offshore exchange volume

US vs offshore exchange volume

GET/api/volume/us-vs-offshore

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
daysintegerOptional365≤ 1095Look-back window in days. Example: 365

Example request

curl -s "https://www.coinboss.com/api/volume/us-vs-offshore?days=365"

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 }`.
sincenumber—Start of the period.
usarray—US-regulated venues.
us[]array—US-regulated venues.
us[][]number—US-regulated venues.
offshorearray—Offshore venues.
offshore[]array—Offshore venues.
offshore[][]number—Offshore venues.
us_share_pctarray—Share of US-regulated venues.
us_share_pct[]array—Share of US-regulated venues.
us_share_pct[][]number%Share of US-regulated venues.

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

Example response

/api/volume/us-vs-offshore?days=365 · Real response captured 2026-11-13 03:58:17 UTC. Long arrays and maps are shortened for display: us had 18629 items; offshore had 18629 items; us_share_pct had 18629 items.

  • {
    • "success": true,
    • "since": 1783349400000,
    • "us": [
      • [ … 2 ],
      • [ … 2 ]
      ],
    • "offshore": [
      • [ … 2 ],
      • [ … 2 ]
      ],
    • "us_share_pct": [
      • [ … 2 ],
      • [ … 2 ]
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
10m
Edge micro-cache
10s
Update frequency
every 10 min; API cache 600 s
Window
days (default 365, max 1095); data starts 2026-07-06
Data sources
Spot volume of US venues (coinbase, kraken) versus all other tracked exchanges, from our 10-minute snapshots.
Exchange coverage
14 spot exchanges; snapshots with fewer than 6 exchanges are skipped
Pagination
none
Units
USD
Method
us = coinbase + kraken; offshore = SUM(all other tracked exchanges)
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:58:17 UTCHTTP 2006 msSchema matchesNewest data point 8m 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/volume/us-vs-offshoreAvailable
Parameters

integer · default 365 · max 1095 — Look-back window in days.

Request URLhttps://www.coinboss.com/api/volume/us-vs-offshore?days=365
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.