Place TWAP Order

Hyperliquid

A time-weighted average price (TWAP) order splits a total size into smaller orders submitted over a chosen duration.

Endpoint

POST /exchange

Request Body

Parameter	Type	Description
`action`*	object	TWAP schedule payload
`nonce`*	number	Replay-protection nonce, e.g., `1701234567890`
`signature`*	object	EIP-712 signature
`expiresAfter`	number	Optional signed expiration time in Unix milliseconds

action

Field	Type	Description
`type`*	string	Must be `"twapOrder"`
`asset`*	string	Unprefixed AssetId: 8 characters for native perps/spot pairs or 16 for HIP-3
`isBuy`*	boolean	`true` for buy, `false` for sell
`sz`*	string	Total TWAP size, e.g., `"0.25"`
`reduceOnly`*	boolean	Reduce-only execution for perps; must be `false` for spot
`durationMinutes`*	number	Positive integer schedule duration in minutes, e.g., `30`
`numSlices`*	number	Positive integer number of TWAP suborders, e.g., `7`
`randomize`*	boolean	Whether to randomize suborder timing within the schedule

Market and Schedule Rules

Native perpetuals and supported spot pairs accept TWAPs. Use a spot-pair AssetId rather than a spot-token AssetId; spot TWAPs cannot be reduce-only.
Assigned HIP-3 TWAPs require an existing active assignment. A TWAP does not allocate a new assignment, and each slice must independently pass admission. Shared-execution HIP-3 markets do not support exposure-increasing TWAPs.
Read twap in Market Metadata for the deployment’s duration and slice-interval bounds. Size must align to the market’s lot precision.
TWAP actions do not accept financing, and slices do not inherit a previous order’s financing authorization.

The implied interval is durationMinutes * 60000 / (numSlices - 1) for multiple slices, or the whole duration for one slice. It must fall within the advertised interval bounds. Admission also requires at least 10 USD of estimated notional per slice, including the first slice after lot-size rounding. Hyperliquid and Polymarket outcome markets do not support TWAPs. Use the exchange signing flow with the user or an approved API wallet.

Response

200: Pending
400: Invalid Schedule

{
  "status": "ok",
  "response": {
    "type": "twapOrder",
    "data": {
      "status": "pending",
      "twapOrderId": "0x1a2b3c..."
    }
  }
}

{
  "error": "Duration must be 5-1440 minutes",
  "code": "VALIDATION_FAILED",
  "timestamp": 1785254400000
}

Result

Field	Type	Description
`status`	`"pending"` \| `"rejected"`	`pending` means the TWAP was saved and scheduled
`twapOrderId`	string \| undefined	Deterministic ID, e.g., `"0x1a2b3c..."`, on accepted requests
`error`	string \| undefined	Rejection reason when processing fails

The invalid-schedule example assumes bounds of 5–1440 minutes; use the deployment’s metadata. Request validation and prechecks return HTTP errors. A rejection during transaction processing can instead return HTTP 200 with response.data.status: "rejected" and error. Read TWAP Order Details using the returned twapOrderId as the query’s twapId, or subscribe to TWAP Updates.

Start Here

Info

Analytics

Exchange

WebSocket

Endpoint

Request Body

action

Market and Schedule Rules

Response

Result

​Endpoint

​Request Body

​action

​Market and Schedule Rules

​Response

​Result

Endpoint

Request Body

action

Market and Schedule Rules

Response

Result