GETAvailableBeta
Research-page statistics
Research-page statistics (liquidation / derivatives / Hyperliquid / ETF / TradFi)
GET
/api/research/stats`avg_funding_rate_pct` is a percentage (0.0021 means 0.0021 %). Totals count only rows that are still updating.
Request
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| topic | string | Required | — | liquidation, derivatives, hyperliquid, etf, tradfi | Topic; 400 if unknown. Example: liquidation |
Example request
curl -s "https://www.coinboss.com/api/research/stats?topic=liquidation"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 }`. |
| data | object | — | Payload. |
| data.topic | string | — | Topic the statistics are for; echoes the `topic` parameter. |
| data.generated_at | string | — | Date-time string. |
| data.stats | object | — | Statistics of the topic; the set of fields depends on the topic. |
| data.stats.total_liquidated_365d_usd | number | USD | Total value of liquidations recorded over the last 365 days, from the daily aggregates. |
| data.stats.total_events_365d | number | count | Number of liquidation orders recorded over the last 365 days. |
| data.stats.total_liquidated_30d_usd | number | USD | Total value of liquidations recorded over the last 30 days. |
| data.stats.long_share_30d_pct | number | % | Long liquidations ÷ (long + short liquidations) over the last 30 days × 100. |
| data.stats.worst_day_365d | object | — | UTC day with the largest liquidation total in the last 365 days: `date` and `total_usd`. |
| data.stats.worst_day_365d.date | string | — | Calendar date (UTC). |
| data.stats.worst_day_365d.total_usd | number | USD | Total. |
| data.stats.largest_single_30d | object | — | Largest single liquidation order of the last 30 days: `symbol`, `exchange` and `value_usd`. |
| data.stats.largest_single_30d.symbol | string | — | Instrument symbol as normalised by CoinBoss (for example BTCUSDT). |
| data.stats.largest_single_30d.exchange | string | — | Exchange id, lower case (for example `binance`). |
| data.stats.largest_single_30d.value_usd | number | USD | Value. |
| data.stats.coins_tracked_30d | number | count | Number of distinct coins with at least one liquidation in the last 30 days. |
| cached | boolean | — | Present and true when the response was served from the 1-hour cache; absent when it was just computed. |
Generated 2026-11-11 23:01 UTC from 1 real responses.
Example response
/api/research/stats?topic=liquidation · Real response captured 2026-11-13 03:53:49 UTC.
- "success"true
- "data"
- "topic""liquidation"
- "generated_at""2026-11-13T03:45:01.925Z"
- "stats"
- "cached"true
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 60m
- Edge micro-cache
- 10s
- Update frequency
- in-memory cache 1 h per topic
- Window
- liquidation: 365d / 30d; derivatives: latest and 24h; tradfi: 30d and all-time; etf: since 2024-01-11
- Data sources
- Headline statistics per topic (liquidation, derivatives, hyperliquid, etf, tradfi) aggregated from our own database; ETF figures come from a third-party source's flow tables.
- Exchange coverage
- topic = liquidation | derivatives | hyperliquid | etf | tradfi
- Pagination
- none
- Units
- USD; percentages
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Beta
Live status
AvailableChecked 2026-11-13 03:53:49 UTCHTTP 2001 msSchema matchesNewest data point 9m old
Availability, last 30 days
99.75% of 407 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/research/statsAvailableParameters
string — Topic; 400 if unknown.
Request URL
https://www.coinboss.com/api/research/stats?topic=liquidationChoose an endpoint and press “Send request”. The response, headers and timing will appear here.
More in this category
- Data-quality matrix (collector view) /api/sd/quality
- API catalog /api/meta/catalog
- Changelog and versioning policy /api/meta/changelog
- Endpoint documentation /api/meta/endpoint
- OpenAPI document /api/meta/openapi
- Data-quality matrix /api/meta/quality
- Service status /api/meta/status
- Checks whether a coin symbol is known to the platform /api/coin-exists
- Map of coin symbol to locally hosted icon path /api/coin-icons
- Coin-page aggregated summary /api/content/coin
- Site-wide section summary /api/content/summary
- Fiat FX rate table /api/currency/fx
- Map of exchange id to locally hosted icon path /api/exchange-icons
- Liveness check /api/health
- Research-page statistics /api/research/stats