Understanding Hyperliquid Order and Cancel Errors in Batched Requests

Summary

This reference explains how Hyperliquid reports errors for batched order and cancel requests. Responses commonly contain one result per requested item, with errors covering validation and trading constraints such as tick-size and minimum-notional rules, insufficient margin or spot balance, reduce-only conflicts, unavailable liquidity, oracle-price limits, and open-interest caps. Cancel failures can indicate that an order was missing, already canceled, or filled.

Some payload-level validation failures reject the entire batch and return a single error rather than one error per order. The document advises API users to account for this response shape when handling callbacks, since the shared error may need to be represented across the batch. It is an operational description of exchange API behavior, not a trading strategy or analysis of market performance. The listed examples are not an exhaustive treatment of every possible API response.

Key ideas

• Batched order and cancel responses often align each result with a requested item.
• Order rejection reasons include trading constraints such as tick size, minimum notional, margin, liquidity, and price limits.
• A cancel error may mean the order was never placed, was already canceled, or has filled.
• Pre-validation can reject an entire batch with one shared error instead of returning an error for each item.
• API clients should handle both per-item errors and whole-batch rejection responses.

Tags

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