GETAvailable
Cross-exchange funding-rate spread ranking
Cross-exchange funding-rate spread ranking
GET
/api/market/funding-spreadRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| limit | integer | Optional | 50 | ≤ 200 | Number of rows to return. Example: 50 |
Example request
curl -s "https://www.coinboss.com/api/market/funding-spread?limit=50"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 }`. |
| now | number | ms | Server time when the response was built. |
| data | array | — | Payload. |
| data[] | object | — | Payload. |
| data[].coin | string | — | Coin symbol, upper case (for example BTC). |
| data[].max_rate | number | fraction | Highest current funding rate of the coin among fresh contracts on all exchanges (per settlement interval, 0.0001 = 0.01 %). |
| data[].min_rate | number | fraction | Lowest current funding rate of the coin among fresh contracts on all exchanges. |
| data[].spread | number | fraction | `max_rate` − `min_rate`; intervals are not normalised, so 1h and 8h rates are compared as published. |
| data[].avg_rate | number | fraction | Simple mean of the coin's current funding rates over all fresh contracts. |
| data[].ex_count | number | — | Number of exchanges. |
Generated 2026-11-11 23:00 UTC from 1 real responses.
Example response
/api/market/funding-spread?limit=50 · Real response captured 2026-11-13 04:02:37 UTC. Long arrays and maps are shortened for display: data had 50 items.
- "success"true
- "now"1794542557227
- "data"
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 60s
- Edge micro-cache
- 10s
- Update frequency
- every 60 s for most venues (written together with tickers; binance dedicated 60 s job); remaining funding jobs and coin-margined contracts every 5 min
- Window
- latest snapshot (no freshness filter)
- Data sources
- Current funding rates polled by in-house collectors from the public REST APIs of 24 perpetual venues (e.g. binance, okx, bybit, bitget, gate, hyperliquid).
- Exchange coverage
- all rows of the latest-funding table including stale ones
- Pagination
- limit (default 50, max 200)
- Sorting
- spread desc
- Units
- funding rate as a raw fraction per funding interval
- Method
- spread = MAX(rate) - MIN(rate) across exchanges per coin (coins listed on >= 2 exchanges)
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
AvailableChecked 2026-11-13 04:02:37 UTCHTTP 20047 msSchema matches
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/market/funding-spreadAvailableParameters
integer · default 50 · max 200 — Number of rows to return.
Request URL
https://www.coinboss.com/api/market/funding-spread?limit=50Choose an endpoint and press “Send request”. The response, headers and timing will appear here.
More 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