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:
| Header | Value |
|---|---|
Content-Type | application/json |
| Field | Required | Type | Description |
|---|---|---|---|
type | Yes | String | Use "frontendOpenOrders". |
user | Yes | String | Account address in 42-character hexadecimal format, for example 0x0000000000000000000000000000000000000000. |
dex | No | String | 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. |
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:
Like what you're reading? Try it yourself โ this link supports ChartedTrader at no cost to you.
Create a Hyperliquid account โ
[
{
"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:
| Field | Example value | What 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}. |
isPositionTpsl | false | Boolean field shown in the response. The docs example uses false for a normal limit order. |
isTrigger | false | Boolean 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. |
oid | 91490942 | Order 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. |
reduceOnly | false | Boolean 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. |
timestamp | 1681247412573 | Timestamp 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 frontendOpenOrders | Purpose in the response shape |
|---|---|
isPositionTpsl | Boolean field shown in the docs response. |
isTrigger | Boolean field shown in the docs response. |
orderType | Order type string. |
origSz | Original size. |
reduceOnly | Reduce-only boolean. |
triggerCondition | Trigger condition string. |
triggerPx | Trigger price string. |
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
- If the response is empty, verify that
useris the actual master or sub-account address, not an agent wallet address. - If you are querying spot open orders, remember that the docs say spot open orders are only included with the first perp dex.
- For API error handling, see Hyperliquid API Error Responses.
Continue with Hyperliquid
Browse the Hyperliquid guide hub for the complete user journey.