historicalOrders | Hyperliquid Info API
Info API
historicalOrders | Hyperliquid Info API
Hyperliquid historicalOrders: fetch a user’s recent orders - both open and finalized - each with its current status and status timestamp.
POST
historicalOrders | Hyperliquid Info API
Credit Cost
1 per call
Processing
Realtime
type: "historicalOrders" is used to fetch a user’s recent orders - both open and finalized - each with its current status and status timestamp.
- Wire-equal to
POST api.hyperliquid.xyz/infowith{"type": "historicalOrders", "user": "0x..."}. - Returns the user’s most recent orders across every coin, open and finalized (filled, canceled, and other terminal states). For only the currently-resting orders, use
openOrdersorfrontendOpenOrders. limitcaps the number returned; the default and maximum is 2000.
status and the millisecond timestamp that status was set. Use it to reconstruct recent order history, audit fills/cancels, or drive an activity view.
Endpoint
Request
string
default:"historicalOrders"
required
Always
"historicalOrders".string
required
The account address in 42-character hex format, e.g.
"0x0000000000000000000000000000000000000000".int
Maximum number of orders to return. Defaults to
2000; values above 2000 are capped at 2000.Example
Response
An array of order entries. Each element pairs theorder with its status and the millisecond timestamp that status took effect.
Field descriptions
limitPx, sz, origSz, and triggerPx are returned as decimal strings, preserving upstream precision. Do not parse them as floats.array<object>
One entry per order.
Related endpoints
orderStatus
Look up the status of a single order by
oid or cloid.openOrders
A user’s currently-resting open orders.
frontendOpenOrders
Open orders with additional frontend fields.
userFills
A user’s recent fills.