Accumulated funding per exchange for one coin
Accumulated funding per exchange for one coin
/api/funding/accumulatedRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| days | integer | Optional | 7 | ≥ 1 · ≤ 90 | Look-back window in days. Example: 7 |
| base | string | Optional | BTC | — | Base coin symbol (uppercase, e.g. BTC). Example: BTC |
Example request
curl -s "https://www.coinboss.com/api/funding/accumulated?base=BTC&days=7"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 }`. |
| base | string | — | Base asset symbol. |
| days | number | — | Daily values or number of days. |
| unit | string | — | Unit of the values in this object. |
| now | number | ms | Server time when the response was built. |
| series | array | — | Time series. |
| series[] | object | — | Time series. |
| series[].exchange | string | — | Exchange id, lower case (for example `binance`). |
| series[].symbol | string | — | Instrument symbol as normalised by CoinBoss (for example BTCUSDT). |
| series[].points | array | — | Data points. |
| series[].points[] | array | — | Data points. |
| series[].points[][] | number | — | Data points. |
| series[].total_pct | number | % | Share of the total. |
| series[].n | number | — | Number of items counted. |
| series[].n_expected | number | count | Settlements a full window should contain: `days` × 24 ÷ `interval_h`; null when the settlement interval cannot be determined. |
| series[].interval_h | number | h | Funding interval. |
| series[].last_time | number | ms | Time of the most recent settlement. |
| series[].history_from | number | ms | Earliest settlement record held for this contract. |
| series[].complete | boolean | — | True when the exchange's history covers the window start and holds at least 90 % of the expected settlements; false means `total_pct` is partial. |
| unavailable | array | — | Items for which no data is available, with reasons. Never reported as 0. |
| unavailable[] | string | — | Items for which no data is available, with reasons. Never reported as 0. |
| method | string | — | Formula / method notes. |
Generated 2026-11-11 23:00 UTC from 4 real responses.
Example response
/api/funding/accumulated?base=BTC&days=7 · Real response captured 2026-11-13 03:57:43 UTC. Long arrays and maps are shortened for display: series had 16 items; series[].points had 21 items.
- "success"true
- "base""BTC"
- "days"7
- "unit""pct"
- "now"1794542263852
- "series"
- "unavailable"
- "backpack"
- "bitfinex"
- "bitunix"
- "edgex"
- "lbank"
- "lighter"
- "paradex"
- "method""settled_records: cum = Σ 交易所实际结算费率(funding_settle,逐笔);1h/4h 结算的交易所每笔都计入;complete=false 为历史起点晚于窗口起点或窗内结算笔数不足(断档)"
Verified samples
Besides the example above, the probe calls this endpoint with these parameters and checks the schema each time.
| Parameters | HTTP | Latency | Result |
|---|---|---|---|
| base=ETH&days=7 | 200 | 42 ms | Pass |
| base=SOL&days=7 | 200 | 41 ms | Pass |
| base=ARKM&days=7 | 200 | 37 ms | Pass |
Checked 2026-11-13 03:57:43 UTC
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 10m
- Edge micro-cache
- 10s
- Update frequency
- hourly (deriv collector on a 60-min timer; self-data settle job at minute >= 6 of each hour)
- Window
- days param, default 7, range 1..90
- Data sources
- Settled funding-rate records polled hourly by in-house collectors from the public funding-history endpoints of 16 venues (e.g. binance, bybit, okx, gate, bitget, hyperliquid).
- Exchange coverage
- 16 venues; binance covers all USDT perpetuals; bybit / okx / gate / bitget cover the top 60 coins by futures volume, htx the top 20; aster, hyperliquid, kucoin, mexc, bingx, kraken, dydx, deribit, whitebit, cryptocom keep one main contract per coin; bitfinex has no public settlement history; history depth differs by venue (binance / bybit / okx / bitget from 2026-04-04, others later); exchanges with a live funding rate but no settlement history are listed under `unavailable`
- Sorting
- total_pct desc
- Units
- unit = 'pct': cumulative settled funding in percent (points = [funding_time ms, cumulative %]); total_pct in percent; interval_h in hours
- Method
- per exchange: cum = running SUM(settled rate) x 100 over the window for the contract with the most settlements; complete = history starts before the window AND settlement count >= 90% of floor(days x 24 / interval_h)
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
Venues without a settlement history (listed in `unavailable`) are not included; they are reported by name instead of being filled with zero.
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 →
| 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
/api/funding/accumulatedPartialinteger · default 7 · min 1 · max 90 — Look-back window in days.
string · default BTC — Base coin symbol (uppercase, e.g. BTC).
https://www.coinboss.com/api/funding/accumulated?days=7&base=BTCMore in this category
- Funding for one coin /api/sd/funding
- OI-weighted / volume-weighted funding history /api/currency/funding-weighted
- Per-exchange funding-rate detail for one coin /api/derivatives/funding-detail
- Accumulated funding per exchange for one coin /api/funding/accumulated
- Funding arbitrage opportunities /api/funding/arbitrage
- Funding-rate chart series for one coin /api/funding/chart
- Current funding rates for one coin across exchanges /api/funding/coin
- Accumulated funding fees /api/funding/fees
- Funding-rate heatmap /api/funding/heatmap
- Funding-rate history for one coin on one exchange /api/funding/history
- Funding-rate matrix /api/funding/matrix
- Funding-rate list per coin /api/market/funding
- Cross-exchange funding-rate spread ranking /api/market/funding-spread