GETAvailable
Checks whether a coin symbol is known to the platform
Checks whether a coin symbol is known to the platform
GET
/api/coin-existsRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| coin | string | Optional | — | — | 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.
| Field | Type | Unit | Description |
|---|---|---|---|
| success | boolean | — | true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`. |
| exists | boolean | — | true when the coin symbol is in the coin list or has at least one liquidation record; false for an empty or unknown symbol. |
| source | string | — | 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.
| Parameters | HTTP | Latency | Result |
|---|---|---|---|
| coin=ETH | 200 | 2 ms | Pass |
| coin=SOL | 200 | 1 ms | Pass |
| coin=ARKM | 200 | 1 ms | Pass |
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 →
| 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/coin-existsAvailableParameters
string — Coin symbol; empty returns exists:false.
Request URL
https://www.coinboss.com/api/coin-exists?coin=BTCChoose an endpoint and press “Send request”. The response, headers and timing will appear here.
More in this category
- Data-quality matrix (collector view) /api/sd/quality
- API catalog /api/meta/catalog
- Changelog and versioning policy /api/meta/changelog
- Endpoint documentation /api/meta/endpoint
- OpenAPI document /api/meta/openapi
- Data-quality matrix /api/meta/quality
- Service status /api/meta/status
- Checks whether a coin symbol is known to the platform /api/coin-exists
- Map of coin symbol to locally hosted icon path /api/coin-icons
- Coin-page aggregated summary /api/content/coin
- Site-wide section summary /api/content/summary
- Fiat FX rate table /api/currency/fx
- Map of exchange id to locally hosted icon path /api/exchange-icons
- Liveness check /api/health
- Research-page statistics /api/research/stats