/api/funding/arbitrage
GETAvailable

Funding arbitrage opportunities

Funding arbitrage opportunities (cross-venue rate gap per coin, at least 2 venues)

GET/api/funding/arbitrage

Request

This endpoint takes no parameters.

Example request

curl -s "https://www.coinboss.com/api/funding/arbitrage"

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 }`.
countnumber—Number of items.
updatednumbermsWhen the data was last updated.
dataarray—Payload.
data[]object—Payload.
data[].basestring—Base asset symbol.
data[].exchangesnumber—Exchanges.
data[].long_exstring—Exchange with the lowest current funding rate for the coin, the leg to go long on.
data[].long_ratenumberfractionCurrent funding rate per settlement interval on `long_ex` (0.0001 = 0.01 %); negative means longs receive funding.
data[].long_ivnumberhFunding settlement interval of the long leg.
data[].short_exstring—Exchange with the highest current funding rate for the coin, the leg to go short on.
data[].short_ratenumberfractionCurrent funding rate per settlement interval on `short_ex` (0.0001 = 0.01 %).
data[].short_ivnumberhFunding settlement interval of the short leg.
data[].long_oi_usdnumber|nullUSDOpen interest of the long-leg contract, updated within 3 hours; null when unavailable.
data[].short_oi_usdnumber|nullUSDOpen interest of the short-leg contract, updated within 3 hours; null when unavailable.
data[].price_spread_pctnumber%Price gap between the legs: (short-leg price − long-leg price) ÷ long-leg price; null when either price is missing.
data[].next_settlenumber|nullmsEarliest upcoming funding settlement time among the two legs; null when neither exchange publishes one.
data[].spreadnumberfraction`short_rate` − `long_rate`, the raw per-interval rate difference without normalising the intervals (0.001 = 0.1 %).
data[].apr_pctnumber% per yearAnnualised percentage.
data[].ratesarray—Rates.
data[].rates[]object—Rates.
data[].rates[].exstring—Exchange id, lower case.
data[].rates[].ratenumber—Funding rate of the current period as published by the exchange.
data[].rates[].ivnumberhFunding settlement interval of this exchange's contract; null when unknown, in which case the exchange is not used as a leg.
data[].rates[].pnumberUSDLast price of this exchange's contract from a ticker updated within 1 hour; null when unavailable.
data[].rates[].oinumber|null—Open interest.
data[].rates[].nftnumber|nullmsNext funding settlement time on this exchange; null when the exchange does not publish it.

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

Example response

/api/funding/arbitrage · Real response captured 2026-11-13 03:57:44 UTC. Long arrays and maps are shortened for display: data had 800 items; data[].rates had 3 items.

  • {
    • "success": true,
    • "count": 1088,
    • "updated": 1794542246888,
    • "data": [
      • { … 15 },
      • { … 15 }
      ]
    }

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; funding rows within 4 h, tickers within 1 h, OI within 3 h
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
USDT perpetuals across venues with a fresh funding rate, ticker and open interest
Pagination
at most 800 rows
Sorting
apr_pct desc
Units
rates as raw fractions per interval; apr_pct in percent per year; volume / OI in USD
Method
for each coin pair the highest-rate and lowest-rate venues: apr_pct = (rate_hi x 24 / interval_hi - rate_lo x 24 / interval_lo) x 365 x 100
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:57:44 UTCHTTP 2006 msSchema matchesNewest data point 17s 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/funding/arbitrageAvailable
Parameters

No parameters.

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