Cancel TWAP Order - Notional Protocol

Hyperliquid

Cancels an active or pending TWAP schedule. Sign with the user or an approved API wallet using the exchange signing flow.

Endpoint

POST /exchange

Request Body

Parameter	Type	Description
`action`*	object	TWAP-cancel 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 `"twapCancel"`
`twapOrderId`*	string	TWAP order ID to cancel, e.g., `"0x1a2b3c4d5e6f7890..."`

Response

200: Canceled
400: Not Cancelable

{
  "status": "ok",
  "response": {
    "type": "twapCancel",
    "data": {
      "status": "canceled",
      "twapOrderId": "0x1a2b3c..."
    }
  }
}

{
  "error": "TWAP order status is 'completed', expected 'active' or 'pending'",
  "code": "VALIDATION_FAILED",
  "timestamp": 1785254400000
}

Result

Field	Type	Description
`status`	`"canceled"` \| `"failed"`	`canceled` means the cancel request was accepted and recorded
`twapOrderId`	string \| undefined	TWAP ID, e.g., `"0x1a2b3c..."`, when available
`error`	string \| undefined	Failure reason when the cancel request is rejected after parsing

Missing or non-cancelable TWAPs return HTTP 400. A rejection during transaction processing can instead return HTTP 200 with response.data.status: "failed" and error. Inspect both forms.