Huobi Global is going to fix one known issue in existing Websocket channel ‘market.$symbol.mbp.$levels’ –
Sometimes the ‘seqNum’ inside refresh message does not match with ‘prevSeqNum’ in incremental message.
Effective Date: June 18, 2020 (GMT+8)
All the changes will be updated on https://huobiapi.github.io/docs/spot/v1/en/
May 28, 2020
Currently, the existing Websocket channel - ‘market.$symbol.mbp.$levels’ supports 150 levels MBP book, but the ‘seqNum’ inside refresh message does not always match with the ‘prevSeqNum’ in incremental updates, which preventing user to align the two types of message.
Since the effective day of this notification, Huobi Global will solve this issue. The ‘seqNum’ inside refresh message user requested via ‘REQ’, should match with the ‘prevSeqNum’ inside one of incremental messages user subscribed via ‘SUB’. User has to make sure that ‘REQ’ request and the ‘SUB’ subscription are coming from same Websocket connection.
API users should evaluate the business impact caused by these issue fixes, further to make relevant change in client’s application, if needed.
All the changes will be updated on Huobi API Docs on the effective date.
Article is closed for comments.