Skip to content
All library documents

Sending Info Requests and Signed Actions over Hyperliquid WebSockets

Article Hyperliquid docs
Read the original

Summary

This documentation explains how to send requests through Hyperliquid’s WebSocket API when those requests would normally use the HTTP API. It distinguishes informational requests from signed actions and describes a common wrapper with a method, request identifier, request type, and payload. A unique identifier is recommended so clients can track outstanding requests.

Responses arrive on the post channel and include the identifier, a response type, and a payload. The response type indicates an info result, action result, or error; errors return a string corresponding to the HTTP status and description. Explorer requests are unsupported over WebSockets. The page outlines the message structure but the listed examples contain no substantive payloads or sample outcomes, and it offers no trading strategy or performance evidence.

Key ideas

  • WebSocket post requests can carry info requests and signed actions normally sent over HTTP.
  • Each request includes a method, identifier, type, and payload.
  • Unique identifiers help clients match responses to outstanding requests.
  • Responses distinguish info results, action results, and errors.
  • Explorer requests are not supported through this WebSocket mechanism.

Tags

CryptoExecution

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.