๐Ÿ”Œ API & Developers

Hyperliquid frontendOpenOrders Info Endpoint: Trigger, Reduce-Only, and Order Type Fields

โš ๏ธ Disclosure: Some links on this page are affiliate links. If you sign up through them, I may earn a commission โ€” at no extra cost to you.
Use frontendOpenOrders when you need the richer order object from Hyperliquid's info endpoint, including trigger, reduce-only, order-type, and original-size fields. It uses the same POST /info endpoint as openOrders, but with a different type value.

Source: Hyperliquid Info endpoint docs

Request

Send a JSON request to:

POST https://api.hyperliquid.xyz/info

Required header:

HeaderValue
Content-Typeapplication/json
Request body:
FieldRequiredTypeDescription
typeYesStringUse "frontendOpenOrders".
userYesStringAccount address in 42-character hexadecimal format, for example 0x0000000000000000000000000000000000000000.
dexNoStringPerp dex name. Defaults to the empty string, which represents the first perp dex. Spot open orders are only included with the first perp dex.
Example request:

curl -s -X POST https://api.hyperliquid.xyz/info \
  -H 'Content-Type: application/json' \
  -d '{
    "type": "frontendOpenOrders",
    "user": "0x0000000000000000000000000000000000000000"
  }'

To include an explicit dex field:

{
  "type": "frontendOpenOrders",
  "user": "0x0000000000000000000000000000000000000000",
  "dex": ""
}

The docs warn that the user value should be the actual master or sub-account address. Using an agent wallet address can lead to an empty result.

Response fields

The docs show a response array containing objects with the following fields:

๐Ÿ’ก Hyperliquid

Like what you're reading? Try it yourself โ€” this link supports ChartedTrader at no cost to you.

Create a Hyperliquid account โ†’
๐ŸŽ You receive: 4% fee discount on first $25M volume ยท per account, lifetime

[
  {
    "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"
  }
]

Field reference:

FieldExample valueWhat to check
coin"BTC"Asset identifier. For perpetuals, this is the coin name returned in the meta response. For spot, the docs describe special formats such as PURR/USDC and @{index}.
isPositionTpslfalseBoolean field shown in the response. The docs example uses false for a normal limit order.
isTriggerfalseBoolean field shown in the response. The docs example uses false for a non-trigger order.
limitPx"29792.0"Limit price shown in the docs example.
oid91490942Order ID.
orderType"Limit"Order type string. The docs examples also show "Market" in related order objects.
origSz"5.0"Original size shown in the docs example.
reduceOnlyfalseBoolean field shown in the response. The docs example uses false; related order-status examples show true for reduce-only orders.
side"A"Side shown in the docs example.
sz"5.0"Size shown in the docs example.
timestamp1681247412573Timestamp in milliseconds.
triggerCondition"N/A"Trigger condition string. The docs example uses "N/A" for a non-trigger order.
triggerPx"0.0"Trigger price string. The docs example uses "0.0" for a non-trigger order.

Difference from openOrders

The basic openOrders request uses the same endpoint and the same user and optional dex fields, but sets:

{
  "type": "openOrders",
  "user": "0x0000000000000000000000000000000000000000"
}

The docs show a basic openOrders response with these fields:

[
  {
    "coin": "BTC",
    "limitPx": "29792.0",
    "oid": 91490942,
    "side": "A",
    "sz": "0.0",
    "timestamp": 1681247412573
  }
]

Compared with openOrders, frontendOpenOrders adds the frontend-related fields:

Added in frontendOpenOrdersPurpose in the response shape
isPositionTpslBoolean field shown in the docs response.
isTriggerBoolean field shown in the docs response.
orderTypeOrder type string.
origSzOriginal size.
reduceOnlyReduce-only boolean.
triggerConditionTrigger condition string.
triggerPxTrigger price string.
Use openOrders when you only need the minimal open-order list. Use frontendOpenOrders when your integration needs trigger, reduce-only, order-type, or original-size fields.

Troubleshooting notes

Create a Hyperliquid account. This is a referral link; if you sign up through it, I may earn a commission. The referred-user 4% fee discount applies to the first $25M of volume per account; Vaults and sub-accounts are excluded.

Continue with Hyperliquid

Browse the Hyperliquid guide hub for the complete user journey.

๐Ÿงฎ Free Hyperliquid calculators

Fee Calculator โ†’
Hyperliquid vs centralized exchange fee comparison
PnL & Liquidation โ†’
Perp PnL + liquidation price
Position Size โ†’
Risk-aware position sizing for HL perps
Hyperliquid

Ready to get started? Use the link below โ€” it helps support ChartedTrader at no cost to you.

Create a Hyperliquid account โ†’
๐ŸŽ You receive: 4% fee discount on first $25M volume ยท per account, lifetime
๐Ÿ“ˆ

About the author

I'm a systematic trader running live strategies on IB (USDJPY momentum) and Hyperliquid (crypto perps). Questions? Reach out.

๐Ÿ“š Related Articles

๐Ÿ”Œ
API & Developers

Hyperliquid orderStatus Info Request: oid, cloid, and Response Shapes

How to query one Hyperliquid order by numeric oid or client order ID using the info endpoint, with request fields, examples, and response shapes.

November 18, 2026 โฑ 4 min read
๐Ÿ”Œ
API & Developers

Hyperliquid l2Book Info Endpoint: Order Book Depth Snapshot Request and Response

Use Hyperliquid's l2Book info request to fetch an L2 order-book snapshot, including required fields, aggregation options, and the documented response shape.

November 18, 2026 โฑ 2 min read
๐Ÿ”Œ
API & Developers

Hyperliquid userRole Info Endpoint: Request, Response Objects, and Python Example

Use the Hyperliquid info endpoint's userRole type to identify whether an address is a user, agent, vault, sub-account, or missing, and inspect the returned data fields.

November 12, 2026 โฑ 2 min read