Liquidation and price stream

One WebSocket connection pushes liquidation prints and price updates. There is no subscribe message: the server sends a `history` frame and a `price_snapshot` frame on connect, then `liquidation` and `price` frames as they happen.

WSwss://www.coinboss.com/ws

Request

There is no subscribe message: the server starts pushing as soon as the connection opens. Reconnect with a delay when the socket closes and backfill the gap over HTTP.

Example request

# WebSocket needs a WS client; with websocat:
websocat "wss://www.coinboss.com/ws"

Response fields

Frame type	Sent	Shape
history	once, on connect	{ "type": "history", "data": [ <liquidation>, ... ] }
price_snapshot	once, on connect	{ "type": "price_snapshot", "data": { "<SYMBOL>": <price>, ... }, "ts": <ms> }
liquidation	every liquidation print	{ "type": "liquidation", "data": <liquidation> }
price	every price change	{ "type": "price", "symbol": "BTCUSDT", "price": <number>, "ts": <ms> }

Example response

No example is stored because the last successful response was too large to display. Call the endpoint in the Playground.

Details

Authentication: None. Public endpoint.
Rate limit: 1200 requests per minute per IP
Server cache: Not cached
Update frequency: Pushed in real time. `liquidation` frames follow exchange liquidation feeds; `price` frames follow futures ticker updates.
Window: `history` contains the most recent liquidation prints at connect time; everything else is live.
Data sources: Exchange liquidation feeds collected by CoinBoss; futures ticker stream.
Timestamps: Unix epoch milliseconds (UTC) in `ts` / `timestamp`.
Response format: json-frames
Stability: Stable

Live status

AvailableChecked 2026-11-13 03:53:49 UTCHTTP 1014 msSchema not checked

Availability, last 30 days

100% 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

WS/wsAvailable

This is a WebSocket stream. Connect to watch real messages arrive; the connection is closed automatically after 25 messages.

Request URLwss://www.coinboss.com/ws

Response

Choose an endpoint and press “Send request”. The response, headers and timing will appear here.

Liquidation and price stream /ws