本頁面為社群翻譯版本,僅供參考;內容以英文原版為準。
查看英文原版 ↗

錯誤回應

下單和撤單錯誤通常以與批量請求長度相同的向量形式返回。

以下是可能的批量錯誤回應列表:

錯誤來源 錯誤類型 錯誤字串
Order Tick Price must be divisible by tick size.
Order MinTradeNtl Order must have minimum value of $10.
Order MinTradeSpotNtl Order must have minimum value of 10 {quote_token}.
Order PerpMargin Insufficient margin to place order.
Order ReduceOnly Reduce only order would increase position.
Order BadAloPx Post only order would have immediately matched, bbo was {bbo}.
Order IocCancel Order could not immediately match against any resting orders.
Order BadTriggerPx Invalid TP/SL price.
Order MarketOrderNoLiquidity No liquidity available for market order.
Order PositionIncreaseAtOpenInterestCap Order would increase open interest while open interest is capped
Order PositionFlipAtOpenInterestCap Order would increase open interest while open interest is capped
Order TooAggressiveAtOpenInterestCap Order rejected due to price more aggressive than oracle while at open interest cap
Order OpenInterestIncrease Order would increase open interest too quickly
Order InsufficientSpotBalance (Spot-only) Order has insufficient spot balance to trade
Order Oracle Order price too far from oracle
Order PerpMaxPosition Order would cause position to exceed margin tier limit at current leverage
Cancel MissingOrder Order was never placed, already canceled, or filled.

重要提示:某些錯誤是負載本身的確定性函數,這些錯誤會作爲預校驗(pre-validation)的一部分提前返回。在這種情況下,整個負載只返回一個錯誤,因爲其中一些錯誤並不針對特定的訂單或撤單。

示例包括:空的訂單批量、非只減倉(reduce-only)的 TP/SL 訂單、訂單價格偏離參考價過大,以及某些形式的 tick size 校驗。

對於使用批量處理的 API 用戶,建議處理一個批量多筆訂單只返回單個錯誤的情況。此時,該回應可以在被送入回調函數之前複製 n 份,因爲整個批量都是因同一原因被拒絕的。

對於使用歷史訂單的 API 用戶,所有撤單/拒絕歷史訂單狀態的列表可在這裡查看。

非官方社群鏡像與翻譯,內容版權歸 Hyperliquid 所有,以英文原版為準。 來源: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/error-responses