Update Leverage

Hyperliquid

Changes the selected leverage for a perpetual market. An assigned HIP-3 position may require asynchronous venue confirmation.

Endpoint

POST /exchange

Request Body

Parameter	Type	Description
`action`*	object	Leverage-update payload
`nonce`*	number	Replay-protection nonce in Unix milliseconds
`signature`*	object	Notional EIP-712 signature with `r`, `s`, and `v`
`expiresAfter`	number	Optional signed expiration time in Unix milliseconds

action

Field	Type	Description
`type`*	string	Must be `"updateLeverage"`
`asset`*	string	Perpetual AssetId as 8- or 16-character unprefixed hex
`isCross`*	boolean	`true` for native cross markets; `false` for assigned HIP-3 markets
`leverage`*	number	Integer from 1 through the market’s applicable leverage maximum

Use hip3.executionPolicy from Market Metadata to distinguish assigned execution ("exclusive_subaccount_v1") from shared execution ("omnibus_v1"). HIP-3 markets using shared execution still fix leverage at the market maximum and reject leverage changes. The user wallet or an approved API wallet may sign. Sign the exact action using the same NotionalExchange domain as order placement.

Response

200: Applied
200: Pending
400: Wrong Margin Mode

{
  "status": "ok",
  "response": {
    "type": "updateLeverage",
    "data": {
      "status": "applied",
      "selectedLeverage": 5
    }
  }
}

{
  "status": "ok",
  "response": {
    "type": "updateLeverage",
    "data": {
      "status": "pending",
      "operationId": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
    }
  }
}

{
  "error": "This market is isolated-only. isCross must be false for leverage changes here.",
  "code": "VALIDATION_FAILED",
  "timestamp": 1785254400000
}

applied confirms a saved selection. On an assigned market without a current assignment, it preselects leverage for the next position. A selection made while a previously active assignment is closing also applies to the next assignment. pending means the request was recorded and still needs venue confirmation. Poll Isolated Operation Status with operationId. Market Trading State exposes the selected, observed, and pending leverage separately; a pending target is not confirmed leverage. Leverage changes can fail when margin is insufficient or an incompatible operation is already in progress. Check isolated.permissions.canChangeLeverage for assigned markets. Cross-market leverage reductions require enough margin for both the position and exposure-increasing open orders.

Start Here

Info

Analytics

Exchange

WebSocket

Endpoint

Request Body

action

Response

​Endpoint

​Request Body

​action

​Response

Endpoint

Request Body

action

Response