GETAvailable
CBBI bull-run composite index
CBBI bull-run composite index
GET
/api/indicators/cbbiRequest
This endpoint takes no parameters.
Example request
curl -s "https://www.coinboss.com/api/indicators/cbbi"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 }`. |
| fetched_at | number | ms | When CoinBoss fetched the data from the source. |
| series | array | — | Time series. |
| series[] | object | — | Time series. |
| series[].name | string | — | Name. |
| series[].data | array | — | Payload. |
| series[].data[] | array | — | Payload. |
| series[].data[][] | number | — | Payload. |
Generated 2026-11-11 23:00 UTC from 1 real responses.
Example response
/api/indicators/cbbi · Real response captured 2026-11-13 03:53:17 UTC. Long arrays and maps are shortened for display: series[].data had 5618 items.
- "success"true
- "fetched_at"1794537797217
- "series"
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 60m
- Edge micro-cache
- 10s
- Update frequency
- on request, cached 12 hours (daily data)
- Window
- full daily history
- Data sources
- CBBI bull-run confidence index from its publisher's public data file.
- Exchange coverage
- BTC cycle confidence index (third-party methodology).
- Sorting
- date ascending
- Units
- index 0-100
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
AvailableChecked 2026-11-13 03:53:17 UTCHTTP 2001 msSchema matchesNewest data point 27.9h old
Availability, last 30 days
100% of 408 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/indicators/cbbiAvailableParameters
No parameters.
Request URL
https://www.coinboss.com/api/indicators/cbbiChoose an endpoint and press “Send request”. The response, headers and timing will appear here.
More in this category
- AHR999 accumulation indicator series /api/indicators/ahr999
- Bitcoin bubble index /api/indicators/bitcoin-bubble
- Full BTC daily close history /api/indicators/btc-history
- Bull-market peak signal checklist /api/indicators/bull-peak-signals
- CBBI bull-run composite index /api/indicators/cbbi
- Derivatives risk index (CoinBoss method) /api/indicators/cdri
- Derivatives composite index (CoinBoss method) /api/indicators/cgdi
- BTC correlation with gold / S&P 500 /api/indicators/correlation
- Correlation matrix of major assets /api/indicators/correlation-matrix
- Crypto legal status by country /api/indicators/crypto-legality
- Cycle-top valuation bands /api/indicators/cycle-caps
- BTC price doubling-time series /api/indicators/doubling-time
- Google search-interest trend /api/indicators/google-trends
- Macro series /api/indicators/macro-series
- Price-forecast model output /api/indicators/price-forecast
- Drawdown-from-ATH series /api/indicators/price-no-turning-back
- Reddit Bitcoin subreddit subscriber count /api/indicators/reddit-subs
- Wikipedia page views /api/indicators/wikipedia-pageviews
- Altcoin season index (CoinBoss method) /api/indices/altseason
- Bottom radar /api/indices/bottom-radar
- Bottom-radar historical case study /api/indices/bottom-radar/case-0819
- BTC multi-factor signal dashboard /api/indices/btc-signal
- Backtest of the BTC signal /api/indices/btc-signal/backtest
- Fear & Greed index /api/indices/fear-greed
- Fear & Greed index (current and history) /api/market/fear-greed
- Signal backtest results /api/signal/backtest/:coin
- Signal monitor dashboard /api/signal/monitor/:coin