orderStatus info request queries one order by either its numeric order ID or its client order ID. According to the official Hyperliquid Info endpoint docs, the request is sent to the info endpoint with type set to "orderStatus".
Request endpoint and body
Send a POST request to:
https://api.hyperliquid.xyz/info
Use the Content-Type: application/json header.
| Field | Required | Type | Description |
|---|---|---|---|
user | Yes | String | Account address in 42-character hexadecimal format, for example 0x0000000000000000000000000000000000000000. |
type | Yes | String | Must be "orderStatus". |
oid | Yes | uint64 or String | Either a u64 order ID, or a 16-byte hex string representing the client order ID. |
cloid field. To query by client order ID, pass the client order ID as the string value of oid.
Example request by numeric order ID
curl -X POST https://api.hyperliquid.xyz/info \
-H 'Content-Type: application/json' \
-d '{
"type": "orderStatus",
"user": "0x0000000000000000000000000000000000000000",
"oid": 91490942
}'
Example request by client order ID
curl -X POST https://api.hyperliquid.xyz/info \
-H 'Content-Type: application/json' \
-d '{
"type": "orderStatus",
"user": "0x0000000000000000000000000000000000000000",
"oid": "1234567890abcdef1234567890abcdef"
}'
The client-order-ID example uses a 32-character hexadecimal string, corresponding to 16 bytes.
Successful response shape
When the order is found, the documented response has top-level status set to "order" and an order object containing the order details, status, and status timestamp.
Like what you're reading? Try it yourself โ this link supports ChartedTrader at no cost to you.
Create a Hyperliquid account with a 4% fee discount on the first $25M of volume; Vaults and sub-accounts are excluded. โ
{
"status": "order",
"order": {
"order": {
"coin": "ETH",
"side": "A",
"limitPx": "2412.7",
"sz": "0.0",
"oid": 1,
"timestamp": 1724361546645,
"triggerCondition": "N/A",
"isTrigger": false,
"triggerPx": "0.0",
"children": [],
"isPositionTpsl": false,
"reduceOnly": true,
"orderType": "Market",
"origSz": "0.0076",
"tif": "FrontendMarket",
"cloid": null
},
"status": "filled",
"statusTimestamp": 1724361546645
}
}
The inner order.order object is the order payload shown in the official documentation. The inner order.status value is one of the documented status strings listed below.
Missing order response
When the order is not found, the documented response is:
{
"status": "unknownOid"
}
Documented order status values
| Status | Explanation |
|---|---|
open | Placed successfully |
filled | Filled |
canceled | Canceled by user |
triggered | Trigger order triggered |
rejected | Rejected at time of placement |
marginCanceled | Canceled because insufficient margin to fill |
vaultWithdrawalCanceled | Vaults only. Canceled due to a user's withdrawal from vault |
openInterestCapCanceled | Canceled due to order being too aggressive when open interest was at cap |
selfTradeCanceled | Canceled due to self-trade prevention |
reduceOnlyCanceled | Canceled reduced-only order that does not reduce position |
siblingFilledCanceled | TP/SL only. Canceled due to sibling ordering being filled |
delistedCanceled | Canceled due to asset delisting |
liquidatedCanceled | Canceled due to liquidation |
scheduledCancel | API only. Canceled due to exceeding scheduled cancel deadline (dead man's switch) |
tickRejected | Rejected due to invalid tick price |
minTradeNtlRejected | Rejected due to order notional below minimum |
perpMarginRejected | Rejected due to insufficient margin |
reduceOnlyRejected | Rejected due to reduce only |
badAloPxRejected | Rejected due to post-only immediate match |
iocCancelRejected | Rejected due to IOC not able to match |
badTriggerPxRejected | Rejected due to invalid TP/SL price |
marketOrderNoLiquidityRejected | Rejected due to lack of liquidity for market order |
positionIncreaseAtOpenInterestCapRejected | Rejected due to open interest cap |
positionFlipAtOpenInterestCapRejected | Rejected due to open interest cap |
tooAggressiveAtOpenInterestCapRejected | Rejected due to price too aggressive at open interest cap |
openInterestIncreaseRejected | Rejected due to open interest cap |
insufficientSpotBalanceRejected | Rejected due to insufficient spot balance |
oracleRejected | Rejected due to price too far from oracle |
perpMaxPositionRejected | Rejected due to exceeding margin tier limit at current leverage |
Related endpoint
If you need to inspect a user's open orders rather than one specific order, see Hyperliquid frontendOpenOrders Info Endpoint: Trigger, Reduce-Only, and Order Type Fields.
Hyperliquid account link
Sign up on Hyperliquid is a referral link. If you sign up, supa.is may receive a commission.Continue with Hyperliquid
Browse the Hyperliquid guide hub for the complete user journey.