๐Ÿ”Œ API & Developers

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

โš ๏ธ 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.
The Hyperliquid 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.

FieldRequiredTypeDescription
userYesStringAccount address in 42-character hexadecimal format, for example 0x0000000000000000000000000000000000000000.
typeYesStringMust be "orderStatus".
oidYesuint64 or StringEither a u64 order ID, or a 16-byte hex string representing the client order ID.
The documented request body does not include a separate 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.

๐Ÿ’ก Hyperliquid

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. โ†’
๐ŸŽ You receive: 4% fee discount on first $25M volume ยท per account, lifetime

{
  "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

StatusExplanation
openPlaced successfully
filledFilled
canceledCanceled by user
triggeredTrigger order triggered
rejectedRejected at time of placement
marginCanceledCanceled because insufficient margin to fill
vaultWithdrawalCanceledVaults only. Canceled due to a user's withdrawal from vault
openInterestCapCanceledCanceled due to order being too aggressive when open interest was at cap
selfTradeCanceledCanceled due to self-trade prevention
reduceOnlyCanceledCanceled reduced-only order that does not reduce position
siblingFilledCanceledTP/SL only. Canceled due to sibling ordering being filled
delistedCanceledCanceled due to asset delisting
liquidatedCanceledCanceled due to liquidation
scheduledCancelAPI only. Canceled due to exceeding scheduled cancel deadline (dead man's switch)
tickRejectedRejected due to invalid tick price
minTradeNtlRejectedRejected due to order notional below minimum
perpMarginRejectedRejected due to insufficient margin
reduceOnlyRejectedRejected due to reduce only
badAloPxRejectedRejected due to post-only immediate match
iocCancelRejectedRejected due to IOC not able to match
badTriggerPxRejectedRejected due to invalid TP/SL price
marketOrderNoLiquidityRejectedRejected due to lack of liquidity for market order
positionIncreaseAtOpenInterestCapRejectedRejected due to open interest cap
positionFlipAtOpenInterestCapRejectedRejected due to open interest cap
tooAggressiveAtOpenInterestCapRejectedRejected due to price too aggressive at open interest cap
openInterestIncreaseRejectedRejected due to open interest cap
insufficientSpotBalanceRejectedRejected due to insufficient spot balance
oracleRejectedRejected due to price too far from oracle
perpMaxPositionRejectedRejected due to exceeding margin tier limit at current leverage

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.

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.

๐Ÿงฎ 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 with a 4% fee discount on the first $25M of volume; Vaults and sub-accounts are excluded. โ†’
๐ŸŽ 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 modify and batchModify: Request Fields, oid/cloid, and always_place

Reference for Hyperliquid's modify and batchModify exchange actions: how oid/cloid identifies the target, the replacement order fields, and the always_place flag.

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

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

Query Hyperliquid's frontendOpenOrders POST /info endpoint, compare it with openOrders, and interpret trigger, reduce-only, orderType, and origSz fields.

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

Hyperliquid Python SDK Tutorial: Build a Bot (2026)

Build a production-ready trading bot on Hyperliquid using the official Python SDK. Covers API wallet security, order execution, WebSocket feeds, and common pitfalls to avoid.

May 6, 2026 โฑ 12 min read