/api/currency/ls-cards
GETAvailable

Coin-page long/short cards

Coin-page long/short cards

GET/api/currency/ls-cards

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
coinstringRequired——Base coin symbol (uppercase, e.g. BTC). Example: BTC

Example request

curl -s "https://www.coinboss.com/api/currency/ls-cards?coin=BTC"

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 }`.
coinstring—Coin symbol, upper case (for example BTC).
dataarray—Payload.
data[]object—Payload.
data[].exchangestring—Exchange id, lower case (for example `binance`).
data[].typestring—Type.
data[].rationumber—Long share divided by short share (1 = balanced).
data[].longnumber—Long share.
data[].shortnumber—Short share.

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

Example response

/api/currency/ls-cards?coin=BTC · Real response captured 2026-11-13 03:57:49 UTC. Long arrays and maps are shortened for display: data had 4 items.

  • {
    • "success": true,
    • "coin": "BTC",
    • "data": [
      • { … 5 },
      • { … 5 }
      ]
    }

Verified samples

Besides the example above, the probe calls this endpoint with these parameters and checks the schema each time.

ParametersHTTPLatencyResult
coin=ETH2005 msPass
coin=SOL2004 msPass
coin=ARKM2004 msPass

Checked 2026-11-13 03:57:49 UTC

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
30s
Edge micro-cache
10s
Update frequency
every 5 min (binance top-trader account ratio and okx taker / top-trader position ratios hourly; long-tail symbols every 30 min)
Window
latest snapshot; rows updated within 24 h
Data sources
Long/short ratios polled by in-house collectors from the public statistics endpoints of 7 exchanges (binance, okx, bybit, bitget, gate, htx, kraken).
Exchange coverage
four cards: binance account ratio, okx account ratio, binance top-trader account ratio, binance top-trader position ratio; fallbacks when missing: binance taker, okx position, then bybit / bitget / gate / htx account ratio
Units
long / short as percentages of 100; ratio = long / short
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:57:49 UTCHTTP 2004 msSchema matches

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/currency/ls-cardsAvailable
Parameters

string — Base coin symbol (uppercase, e.g. BTC).

Request URLhttps://www.coinboss.com/api/currency/ls-cards?coin=BTC
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.