AsyncAPI channel · Huobi · Huobi / HTX WebSocket API

market.{symbol}.mbp.{levels}

Market By Price (incremental) updates. Use `seqNum` / `prevSeqNum` to chain updates and de-duplicate. Served on the `/feed` endpoint.

Open source AsyncAPI → All Huobi channels Huobi provider profile
Provider: Huobi AsyncAPI: v2.6.0 Spec: Huobi / HTX WebSocket API Operations: 2 Messages: 4

Channel address

market.{symbol}.mbp.{levels}

Parameters

Operations

publish
subMbp
pushMbp

Messages

V1SubscribeRequest
Subscribe to a v1 market-data topic.
Content-Type:
V1UnsubscribeRequest
Unsubscribe (v1)
Content-Type:
V1Request
Request a historical / snapshot payload for a topic.
Content-Type:
MbpIncrementalPush
MBP Incremental Push
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.