Skip to main content
POST
/
info
info (twapHistory)
curl --request POST \
  --url https://api.hyperliquid.xyz/info \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "twapHistory",
  "user": "0x1442ad477ded1b0028b57621aa7b6f7eadb8f568"
}
'
[
  {
    "time": 123,
    "state": {},
    "status": {},
    "twapId": 123
  }
]
You can only use this endpoint on the official Hyperliquid public API. It is not available through Chainstack, as the open-source node implementation does not support it yet. See Hyperliquid methods for the full availability breakdown.
The info endpoint with type: "twapHistory" returns a user’s TWAP (time-weighted average price) order history — each record’s creation time, state, and current status.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

​
Request body

  • type (string, required) — The request type. Must be "twapHistory".
  • user (string, required) — Address in 42-character hexadecimal format.

​
Response

Returns an array of TWAP history records. Each record contains:
  • time (integer) — Creation time of the record (seconds since epoch).
  • state (object) — The state of the TWAP order (coin, size, executed amounts, side, and related fields).
  • status (object) — The current status, for example {"status": "finished"}, {"status": "activated"}, {"status": "terminated"}, or {"status": "error", "description": "..."}.
  • twapId (integer) — The ID of the TWAP order.

​
Example request

curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"type": "twapHistory", "user": "0x1442ad477ded1b0028b57621aa7b6f7eadb8f568"}' \
  https://api.hyperliquid.xyz/info

​
Example response

[]
The example returns an empty array because the queried address has no TWAP history. An account with TWAP orders returns an array of history records as described above.

​
Use cases

The info endpoint with type: "twapHistory" is useful for:
  • Auditing a user’s past TWAP orders
  • Trading dashboards that show TWAP execution history
  • Analyzing TWAP order outcomes over time

Body

application/json
​
type
enum<string>
default:twapHistory
required

Request type

Available options:
twapHistory
​
user
string
default:0x1442ad477ded1b0028b57621aa7b6f7eadb8f568
required

User address in 42-character hexadecimal format.

Response

200 - application/json

The user's TWAP order history.

​
time
integer

Creation time of the record (seconds since epoch).

​
state
object

State of the TWAP order.

​
status
object

Current status of the TWAP order (e.g., finished, activated, terminated, error).

​
twapId
integer

ID of the TWAP order.

Last modified on June 24, 2026