scheduleCancel is a Hyperliquid exchange endpoint action that schedules a future cancel-all operation. If you include a future time, Hyperliquid cancels all open orders when that time arrives. If you omit time, the scheduled cancel operation is removed.
As of 2026-11-11, the official Hyperliquid exchange endpoint documentation states the following rules:
- The scheduled time must be at least 5 seconds after the current time.
- When the scheduled time arrives, all open orders are canceled.
- Each trigger increments a trigger count.
- The maximum number of triggers per day is 10.
- The trigger count resets at 00:00 UTC.
Request endpoint
Send a signed request to the official Hyperliquid exchange endpoint:
POST https://api.hyperliquid.xyz/exchange
The action object uses:
{
"type": "scheduleCancel",
"time": 1234567890123
}
💡 Hyperliquid
Like what you're reading? Try it yourself — this link supports ChartedTrader at no cost to you.
Create a Hyperliquid account →🎁 You receive: 4% fee discount on first $25M volume · per account, lifetime
To remove an existing scheduled cancel, omit time:
{
"type": "scheduleCancel"
}
The documentation lists time as optional. Replace the example value with a valid future time value accepted by the endpoint; the key constraint is that it must be at least 5 seconds after the current time.
Required and optional fields
| Field | Required | Description |
|---|---|---|
action | Yes | Must include "type": "scheduleCancel". Include time to schedule a cancel-all; omit time to remove the scheduled cancel. |
nonce | Yes | Recommended to use the current timestamp in milliseconds. |
signature | Yes | Signature object for the request. |
vaultAddress | No | Address of a subaccount or vault when acting on its behalf. |
expiresAfter | No | Timestamp in milliseconds after which the action is rejected. |
vaultAddress to the subaccount or vault address.
scheduleCancel vs expiresAfter
They are not the same thing:
scheduleCancelschedules a future cancel-all of open orders. It is a separate action with its own trigger limit.expiresAfteris an optional deadline on an action. If the action is still processed after that timestamp, it is rejected.
expiresAfter field consume 5x the usual address-based rate limit. User-signed actions such as Core USDC transfer do not support expiresAfter. See Hyperliquid API expiresAfter: Action Deadline, Rejection, and 5x Rate-Limit Cost for that mechanism.
Practical notes
- Use
scheduleCancelas a safety mechanism when you want all open orders canceled if a bot or process stops updating the schedule. - Remember that the trigger limit is 10 per UTC day, so repeated scheduled cancellations can exhaust the daily allowance.
- A scheduled cancel-all affects all open orders for the account or vault being signed for, so test the behavior in a low-risk environment before relying on it in production.
Continue with Hyperliquid
Browse the Hyperliquid guide hub for the complete user journey.