Feeds / Crypto exchanges (live)

KuCoin

Spot. WebSocket diffs, seeded by a REST snapshot.

Live in productionWebSocketREST snapshot of 100 levels

Live now

-
books live
-
messages / s
-
level changes / s
-
KB / s

Messages / s and KB / s are what our handler receives from the exchange (KB after decompression, REST snapshots included); level changes / s are counted after normalization, for the markets we publish.

Open live books Replay

How we connect

Market
Spot
WebSocket
wss://ws-api-spot.kucoin.com/?token={public token}
Channels
/market/level2:{symbols} — order book increments
/market/match:{symbols} — trades
Update model
WebSocket diffs, seeded by a REST snapshot.
Snapshot (REST)
https://api.kucoin.com/api/v1/market/orderbook/level2_100?symbol={SYMBOL}
Sequencing
Diffs are buffered until the REST snapshot arrives; buffered diffs with sequenceEnd <= the snapshot sequence are dropped and the rest replayed. After that, sequenceStart is not checked against the previous sequenceEnd + 1.
On a gap
No in-stream gap check; on reconnect (socket error, close, or 30 s without data) sync is reset and REST snapshots re-fetched. Snapshots are also re-applied every 10 minutes.
Depth
REST snapshot of 100 levels
Authentication
none (a public connect token from /api/v1/bullet-public, no API key)
Heartbeat
Client ping every 15 s; WebSocket pings answered. Reconnect after 30 s without data.
Symbol format
BTC-USDT

Subscribe message

{"id":"1","type":"subscribe","topic":"/market/level2:BTC-USDT,ETH-USDT,...","response":false}

What our handler takes care of

Instruments

loading...

Upcoming and recent changes

2026-11-20InfoResponse field now supports a futures symbol typeMay affect market data
A response field of an API now supports a new symbol type for futures, where previously only spot was supported.
Details

The page text is truncated and does not name the endpoint or field. Futures is now supported in addition to spot. Our handler only uses spot order book and trade data, so check that none of the REST or WebSocket calls it uses return this field.

Our handler: The endpoint and field are not named in the text, so it cannot be ruled out that it touches market data symbol info.

Source ↗

2026-11-20InfoNew small-balance to KCS conversion endpoints
KuCoin added endpoints to list convertible small balances, convert up to 20 currencies into KCS, query a conversion order and fetch conversion order history.
Details

These are account-level functions for FUNDING or SPOT accounts covering eligible currencies, conversion requests, order lookup and paginated history. They need no change for public market data consumers.

Our handler: These are account and conversion endpoints, not the public level2 or match channels or the REST order book snapshot.

Source ↗

2026-11-20InfoAPI rate limit pool change in ManagementMay affect market data
The changelog lists an api-rate-limit-pool change under Management, with no details given.
Details

The text gives no specifics on what changed in the rate limit pool. It appears to relate to account management rather than public data. Review rate limit documentation if our REST snapshot calls are throttled.

Our handler: Rate limits could affect REST snapshot requests to level2_100, but the text gives no details.

Source ↗

2026-11-20InfoUTA API V2 added
KuCoin added a Unified Trading Account (UTA) API V2.
Details

No further detail is given. UTA is an account and trading product. Our handler uses the classic spot WebSocket and REST endpoints and needs no change.

Our handler: UTA API V2 is a separate account and trading API, not the spot level2, match or snapshot endpoints we use.

Source ↗

2026-11-20Action neededError code 111235 replaces 111202 and 111209May affect market data
A new error code 111235 (Service busy, reduce request frequency and retry later) replaces codes 111202 and 111209, which will be deprecated.
Details

No date is given for the deprecation. Clients that match on error codes 111202 or 111209 should also handle 111235. This appears tied to the UTA API, so it is likely irrelevant to our public feed, but check any error handling keyed on these codes.

Our handler: The text does not say which endpoints return these codes, and our REST snapshot error handling could be affected if it keys on them.

Source ↗

2026-11-06InfoClassic account summary V3 response changed; sub-account mode field added
Get Account Summary Info (V3) now returns a new response structure. A new optional mode field was added to the Add Sub Account endpoints, and a UTA private funding fee settlement channel was added.
Details

Classic REST Get Account Summary Info (V3) removes the subQuantity-type fields (subQuantity, spotSubQuantity, futuresSubQuantity, marginSubQuantity, optionSubQuantity and the max* variants). It adds level, maxSharedSubCount and usedSharedSubCount, which are now required. Add Sub Account (UTA and Classic) gets an optional mode field (CLASSIC or UNIFIED). The UTA WebSocket private channel FundingFeeSettle was added. All of this is account-related, so a public market data client needs to do nothing.

Our handler: Only account summary, sub-account and private WebSocket items changed; public level2 and match feeds are not involved.

Source ↗

Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed

Official documentation

KuCoin — WebSocket orderbook increment (/market/level2) ↗www.kucoin.comKuCoin — WebSocket trades (/market/match) ↗www.kucoin.comKuCoin — get public token (bullet-public) ↗www.kucoin.comKuCoin — get part order book (REST) ↗www.kucoin.comKuCoin — rate limits ↗www.kucoin.comKuCoin — changelog ↗www.kucoin.com

Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.