Update leverage setting
Limit: 5 requests per 60 second per user
POST /v1/client/leverages
Update leverage settings. This endpoint supports two modes:
Single symbol mode: When symbol is provided, update leverage for that specific symbol.
Batch mode: When symbol is omitted, set leverage for all symbols in a single atomic operation. Each symbol’s new leverage will be adjusted to min(requested_leverage, symbol_max_leverage).
For example, if BTC max leverage is 100, ETH max leverage is 100, and NEAR max leverage is 10, and the user requests leverage = 20, the result will be: BTC = 20, ETH = 20, NEAR = 10.
Batch update behavior with margin modes:
- Cross margin symbols: A margin check is performed assuming all cross-margin symbols are updated to the new leverage. Either all cross-margin symbol leverages are updated successfully, or none are updated.
- Isolated margin symbols: The leverage update will only apply to symbols with no active isolated positions or pending orders. The update for isolated margin symbols will always go through for eligible symbols.
Validation Logic:
-
Check the leverage range is eligible
-
Check if the position notional under the updated leverage is acceptable
max_notional = (1 / (symbol_leverage * imr_factor)) ^ (1/0.8)symbol_leverage_max = round down to int → min(1 / (imr_factor * notional ^ 0.8), 1/base_imr)
-
Check if the margin is enough
Headers
Timestamp of the signed request in milliseconds.
Account ID of the authenticated account.
Public orderly key used to sign the request.
Signature of the request payload generated with the orderly key.