AsyncAPI channel · Blockchain.com · Blockchain.com WebSocket APIs

/mercury-gateway/v1/ws#l3

Level 3 (order-by-order) book per symbol. Each entry has order `id`, `px`, and `qty`. Updates with `qty:0` indicate the order should be removed.

Open source AsyncAPI → All Blockchain.com channels Blockchain.com provider profile
Provider: Blockchain.com AsyncAPI: v2.6.0 Spec: Blockchain.com WebSocket APIs Operations: 2 Messages: 3

Channel address

/mercury-gateway/v1/ws#l3

Operations

publish
subscribeL3
Subscribe / unsubscribe to L3 order book updates for a symbol.
receiveL3
Receive L3 snapshot and incremental updates.

Messages

ExchangeSubscribeSymbolAction
Subscribe / unsubscribe to a per-symbol channel
Content-Type:
ExchangeAdminEvent
Subscription admin event (subscribed / unsubscribed / rejected)
Content-Type:
ExchangeL3Event
L3 order book snapshot / update
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.