frontendOpenOrders | Hyperliquid info

​

Parameters

​

Request body

• type (string, required) — The request type. Must be "frontendOpenOrders" to retrieve user’s open orders with frontend formatting.
• user (string, required) — Address in 42-character hexadecimal format (e.g., 0x31ca8395cf837de08b24da3f660e77761dfb974b).
• dex (string, optional) — Perp dex name. Defaults to the empty string which represents the first perp dex. Spot open orders are only included with the first perp dex.

​

Response

​

Core order fields

• coin (string) — Trading pair or asset symbol (e.g., “BTC”, “ETH”)
• limitPx (string) — Limit price of the order in string format for precision
• oid (integer) — Order ID, a unique identifier for the order
• side (string) — Order side:
  • "A" — Ask (sell order)
  • "B" — Bid (buy order)
• sz (string) — Current order size in string format for precision
• timestamp (integer) — Order creation timestamp in milliseconds

​

Frontend-enhanced fields

• origSz (string) — Original order size when the order was created
• orderType (string) — Human-readable order type (e.g., “Limit”, “Market”, “Stop”, “Stop Limit”)
• triggerCondition (string) — Trigger condition for conditional orders
• triggerPx (string) — Trigger price for conditional orders
• reduceOnly (boolean) — Whether this is a reduce-only order that can only decrease position size
• isPositionTpsl (boolean) — Whether this is a position take-profit/stop-loss order
• isTrigger (boolean) — Whether this is a trigger order

​

Order side interpretation

• “A” (Ask): Sell order - user wants to sell the asset at the specified price
• “B” (Bid): Buy order - user wants to buy the asset at the specified price

​

Order types

• Limit: Standard limit order at a specific price
• Market: Immediate execution at current market price
• Stop: Stop-loss order triggered when price reaches trigger level
• Stop Limit: Stop order that becomes a limit order when triggered

​

Example request

curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"type": "frontendOpenOrders", "user": "0x31ca8395cf837de08b24da3f660e77761dfb974b"}' \
  https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info

​

Example response

[
    {
        "coin": "BTC",
        "isPositionTpsl": false,
        "isTrigger": false,
        "limitPx": "29792.0",
        "oid": 91490942,
        "orderType": "Limit",
        "origSz": "5.0",
        "reduceOnly": false,
        "side": "A",
        "sz": "5.0",
        "timestamp": 1681247412573,
        "triggerCondition": "N/A",
        "triggerPx": "0.0"
    }
]

​

Use case

• Display comprehensive order information in trading interfaces
• Show order types and trigger conditions in user-friendly formats
• Implement advanced order management features with conditional logic
• Build order books and trading dashboards with enhanced metadata
• Provide detailed order tooltips and information panels
• Support complex order types like stop-loss and take-profit orders
• Display reduce-only orders with appropriate visual indicators
• Create order history views with complete order context
• Implement order modification workflows with type-specific handling
• Build mobile trading apps with condensed but complete order data
• Support advanced trading strategies requiring order type awareness
• Provide audit trails and order analytics with detailed classifications