AsyncAPI channel · Hyperliquid · Hyperliquid WebSocket API

/

Single WebSocket channel for all Hyperliquid subscriptions and post-requests. Clients publish subscribe/unsubscribe/post messages and receive subscriptionResponse, post, and per-feed data messages.

Open source AsyncAPI → All Hyperliquid channels Hyperliquid provider profile
Provider: Hyperliquid AsyncAPI: v2.6.0 Spec: Hyperliquid WebSocket API Operations: 2 Messages: 22

Channel address

/

Operations

publish
clientSend
Messages sent by the client to the server.
clientReceive
Messages received by the client from the server.

Messages

subscribe
Subscribe to a Hyperliquid feed.
Content-Type:
unsubscribe
Unsubscribe from a previously subscribed feed.
Content-Type:
post
Send a REST-style info or action request over the WebSocket. The response is delivered on the `post` channel with the same `id`.
Content-Type:
subscriptionResponse
Acknowledgement of a subscribe/unsubscribe request.
Content-Type:
postResponse
Post Response
Content-Type:
allMids
Content-Type:
notification
Content-Type:
webData2
Content-Type:
candle
Content-Type:
l2Book
Content-Type:
trades
Content-Type:
bbo
Content-Type:
orderUpdates
Content-Type:
user
User events. Note: while the subscription `type` is `userEvents`, the channel field on incoming messages is `user`.
Content-Type:
userFills
Content-Type:
userFundings
Content-Type:
userNonFundingLedgerUpdates
Content-Type:
activeAssetCtx
Content-Type:
activeAssetData
Content-Type:
userTwapSliceFills
Content-Type:
userTwapHistory
Content-Type:
pong
Server keep-alive response to a client `ping`.
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.