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

Exchange reserves history

Exchange reserves history

GET/api/reserves/history

Request

This endpoint takes no parameters.

Example request

curl -s "https://www.coinboss.com/api/reserves/history"

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 }`.
updated_atnumbermsWhen this row was last updated.
seriesarray—Time series.
series[]object—Time series.
series[].keystring—Key.
series[].namestring—Name.
series[].dataarray—Payload.
series[].data[]array—Payload.
series[].data[][]number—Payload.

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

Example response

/api/reserves/history · Real response captured 2026-11-13 03:58:16 UTC. Long arrays and maps are shortened for display: series had 10 items; series[].data had 1422 items.

  • {
    • "success": true,
    • "updated_at": 1794511714993,
    • "series": [
      • { … 3 },
      • { … 3 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
60m
Edge micro-cache
10s
Update frequency
fetched on request, cached 12 h in memory and on disk; API cache 3600 s
Window
full daily history provided by a third-party source
Data sources
Daily reserve (TVL) history per exchange fetched from a third-party source's protocol endpoint.
Exchange coverage
The same 10 exchanges as /api/reserves/overview
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 03:58:16 UTCHTTP 2002 msSchema matchesNewest data point 8.5h old

Availability, last 30 days

99.27% 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/reserves/historyAvailable
Parameters

No parameters.

Request URLhttps://www.coinboss.com/api/reserves/history
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.