Skip to main content
POST
/
v1
/
info
/
openOrders
Get Open Orders
curl --request POST \
  --url https://api.hypereth.io/v1/info/openOrders \
  --header 'Content-Type: application/json' \
  --data '{
  "type": "openOrders",
  "user": "0x31ca8395cf837de08b24da3f660e77761dfb974b"
}'
[
  {
    "coin": "BTC",
    "side": "A",
    "limitPx": "43250.0",
    "sz": "0.5",
    "oid": 127244980388,
    "timestamp": 1681923833000,
    "origSz": "1.0",
    "cloid": "my_order_001"
  }
]

Body

application/json
​
type
enum<string>
required

Request type identifier

Available options:
openOrders
​
user
string
required

User's Ethereum address

Example:

"0x31ca8395cf837de08b24da3f660e77761dfb974b"

​
dex
string
default:""

Perp dex name for multi-dex support

Response

List of open orders

List of user's open orders

​
coin
string
required

Trading pair symbol (e.g., "BTC", "ETH"). For spot pairs, includes token symbols.

Example:

"BTC"

​
side
enum<string>
required

Order side indicator:

  • "A" = Ask (sell order)
  • "B" = Bid (buy order)
Available options:
A,
B
​
limitPx
string
required

Limit price for the order. String format preserves precision. For market orders, this may be the worst acceptable price.

Example:

"43250.0"

​
sz
string
required

Remaining unfilled size of the order. Decreases as order is filled. String format preserves precision for fractional amounts.

Example:

"0.5"

​
oid
integer
required

Unique order identifier assigned by the exchange. Used for order status checks, modifications, and cancellations.

Example:

127244980388

​
timestamp
integer
required

Order creation timestamp in milliseconds since Unix epoch. Used for order aging and time-in-force calculations.

Example:

1681923833000

​
origSz
string

Original order size before any fills

Example:

"1.0"

​
cloid
string

Optional client order ID provided by user for order tracking. Can be used instead of oid for order operations.

Example:

"my_order_001"