Open Orders - Notional Protocol

HyperliquidPolymarket

Returns currently working orders, newest first, including local TP/SL, spot-prefunding orders, and pending or canceling Polymarket orders. Other orders awaiting venue acceptance may not yet appear. An empty array is a valid response.

Endpoint

POST /info

Request Body

Parameter	Type	Description
`type`*	string	Must be `"openOrders"`
`user`*	string	User wallet address, e.g., `"0x1111111111111111111111111111111111111111"`

Response

200: Open Orders

[
  {
    "coin": "BTC",
    "marketAssetId": "00020000",
    "isPositionTpsl": false,
    "isTrigger": true,
    "limitPx": "49000.00",
    "oid": "0x1a2b3c4d5e6f7890...",
    "orderType": "stop_limit",
    "origSz": "0.1",
    "reduceOnly": false,
    "side": "B",
    "sz": "0.1",
    "timestamp": 1701234567890,
    "triggerCondition": "tp",
    "triggerPx": "50000.00",
    "parentOrderId": null,
    "status": "waitingForTrigger"
  }
]

Response Fields

Field	Type	Description
`oid`	string	Notional order ID, e.g., `"0x1a2b3c4d5e6f7890..."`
`marketAssetId`	string	Unprefixed AssetId for the order’s market
`filledSz`	string \| undefined	Canonical matched size for Polymarket orders
`parentOrderId`	string \| null	TP/SL parent ID, e.g., `"0x4d5e6f..."`, or `null`
`protocolSpotTransferStatus`	string \| undefined	Funding status for a spot buy, e.g., `"pending"`
`status`	string \| undefined	Current order status, e.g., `"waitingForTrigger"`

For Polymarket orders backed by canonical fill-settlement facts, use filledSz for executed size instead of deriving origSz - sz. Price improvement can fill more shares than origSz while remaining within the signed quote budget. The field is absent on legacy rows without settlement facts and on non-Polymarket orders.