Spot. WebSocket diffs, seeded by a REST snapshot.
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 Replaywss://ws-api-spot.kucoin.com/?token={public token}https://api.kucoin.com/api/v1/market/orderbook/level2_100?symbol={SYMBOL}BTC-USDT{"id":"1","type":"subscribe","topic":"/market/level2:BTC-USDT,ETH-USDT,...","response":false}
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.
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.
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.
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.
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.
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.
Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed
Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.