24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/coins/search
GETAvailable

Coin search

Coin search

GET/api/coins/search
Coin records not updated for more than 48 hours are returned with `market_cap` and `mcap_rank` set to `null` and `is_stale: true`.

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
qstringOptional——Search keyword; empty returns an empty array. Example: btc

Example request

curl -s "https://www.coinboss.com/api/coins/search?q=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 }`.
dataarray—Payload.
data[]object—Payload.
data[].coinstring—Coin symbol, upper case (for example BTC).
data[].namestring—Name.
data[].image_urlstring—Same-origin icon path served by CoinBoss; null when no verified icon exists.
data[].market_capstring(decimal)—Market capitalisation.
data[].pricestring(decimal)—Last price in the quote currency (USD or USDT unless stated).

Generated 2026-11-11 22:59 UTC from 1 real responses.

Example response

/api/coins/search?q=btc · Real response captured 2026-11-13 03:57:28 UTC. Long arrays and maps are shortened for display: data had 20 items.

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

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
30s
Edge micro-cache
10s
Update frequency
full list every 6 h, top 2,500 hourly; API cache 30 s
Data sources
Coin search over the third-party market-data aggregator-backed coin master list.
Exchange coverage
third-party market-data aggregator full coin list (about 20,400 rows)
Pagination
fixed top 20
Sorting
market cap desc (rows without market cap last)
Units
USD
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:57:28 UTCHTTP 20012 msSchema matches

Availability, last 30 days

99.76% 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 →

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/coins/searchAvailable
Parameters

string — Search keyword; empty returns an empty array.

Request URLhttps://www.coinboss.com/api/coins/search?q=btc
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.