/api/coin-exists
GETAvailable

Checks whether a coin symbol is known to the platform

Checks whether a coin symbol is known to the platform

GET/api/coin-exists

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
coinstringOptional——Coin symbol; empty returns exists:false. Example: BTC

Example request

curl -s "https://www.coinboss.com/api/coin-exists?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 }`.
existsboolean—true when the coin symbol is in the coin list or has at least one liquidation record; false for an empty or unknown symbol.
sourcestring—Where the value comes from.

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

Example response

/api/coin-exists?coin=BTC · Real response captured 2026-11-13 03:53:48 UTC.

  • {
    • "success": true,
    • "exists": true,
    • "source": "coins"
    }

Verified samples

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

ParametersHTTPLatencyResult
coin=ETH2002 msPass
coin=SOL2001 msPass
coin=ARKM2001 msPass

Checked 2026-11-13 03:29:29 UTC

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
5m
Edge micro-cache
10s
Update frequency
coin master list refreshed every 6 h (top 2,500 hourly); API cache 300 s
Data sources
Existence check against the coin master list (third-party market-data aggregator full coin list) with a fallback to any symbol ever seen in the liquidation stream.
Exchange coverage
About 16,500 third-party market-data aggregator coins plus symbols observed in liquidation feeds
Pagination
none
Method
exists = symbol found in coins (source="coins") else in liquidations (source="liquidations")
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:53:48 UTCHTTP 2001 msSchema matches

Availability, last 30 days

99.75% of 407 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/coin-existsAvailable
Parameters

string — Coin symbol; empty returns exists:false.

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