/api/indices/btc-signal/backtest
GETAvailable

Backtest of the BTC signal

Backtest of the BTC signal

GET/api/indices/btc-signal/backtest

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
daysintegerOptional180≥ 30 · ≤ 372Look-back window in days. Example: 180

Example request

curl -s "https://www.coinboss.com/api/indices/btc-signal/backtest?days=180"

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 }`.
dimstring—Dimension that was backtested (`liq`, the liquidation score).
daysnumber—Daily values or number of days.
nnumber—Number of items counted.
hitsnumbercountDays on which the direction predicted by the score matched the next day's price direction.
accuracynumber%`hits` ÷ `n` × 100.
strongNnumbercountDays whose absolute score was 50 or more.
strongAccuracynumber%Hit rate on the `strongN` days only.
baselinenumber%Coin-flip reference for comparison (50).
samplesarray—Number of samples.
samples[]object—Number of samples.
samples[].dstring—Calendar date (UTC).
samples[].scorenumber—Score.
samples[].nextRetnumber%Open-to-close price change of BTC on the following day.
samples[].prednumber—Predicted direction from the sign of the score: 1 up, −1 down, 0 none.
samples[].actualnumber—Actual direction from the sign of `nextRet`: 1 up, −1 down, 0 flat.
samples[].hitboolean—true when `pred` is not 0 and equals `actual`.

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

Example response

/api/indices/btc-signal/backtest?days=180 · Real response captured 2026-11-13 04:03:35 UTC. Long arrays and maps are shortened for display: samples had 60 items.

  • {
    • "success": true,
    • "dim": "liq",
    • "days": 180,
    • "n": 167,
    • "hits": 81,
    • "accuracy": 48.5,
    • "strongN": 93,
    • "strongAccuracy": 43,
    • "baseline": 50,
    • "samples": [
      • { … 6 },
      • { … 6 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
10m
Edge micro-cache
10s
Update frequency
recomputed on request (10 min cache)
Window
last 180 days by default (`days` 30-372)
Data sources
In-house backtest of the liquidation-imbalance signal against next-day BTC direction, using self-collected exchange liquidations and exchange daily klines.
Exchange coverage
BTC only; covers the liquidation dimension only (other five dimensions are not backtested); history limited to the period the liquidation collectors have been running.
Sorting
date ascending (last 60 samples returned)
Units
accuracy in percent; sample scores -100..+100
Method
For each day, sign of (short liquidations - long liquidations) / total is compared with the next daily candle direction; days with under 1M USD of liquidations are skipped; 'strong' accuracy uses |score| >= 50.
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 04:03:35 UTCHTTP 2001 msSchema matchesNewest data point 28.1h old

Availability, last 30 days

99.76% of 409 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/indices/btc-signal/backtestAvailable
Parameters

integer · default 180 · min 30 · max 372 — Look-back window in days.

Request URLhttps://www.coinboss.com/api/indices/btc-signal/backtest?days=180
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.