Skip to main content
POST
Update leverage settings
Leverage settings are updated via the unified POST /order endpoint. Send a transaction with an updateUserSettings action in the actions array.

Transaction Envelope

Every request to POST /order has this shape:
For user settings, the action is a single updateUserSettings object.

Settings Fields

Max Leverage (m)

Object mapping symbol to maximum leverage (1.0–50.0). Cannot exceed the market’s configured maximum. Constraints:
  • Leverage is clamped between 1.0 and 50.0
  • Cannot exceed the market’s configured maximum leverage
  • Lower leverage reduces liquidation risk

Request Example


Response

Same OrderResponse format as other actions. For update user settings, success returns an empty or applied status; settings are applied to the account.

Before You Start

See the Transaction Signing guide for how to sign your requests.Nonce: Use a unique value (e.g. timestamp in nanoseconds): BigInt(Date.now()) * 1_000_000n

Body

application/json

Transaction with a single updateUserSettings action

actions
Update user settings (updateUserSettings) · object[]
required

Must contain exactly one updateUserSettings action

nonce
integer<int64>
required

Unique nonce (e.g. nanoseconds)

account
string
required

Account public key (base58)

signer
string
required

Signer public key (base58)

signature
string
required

Ed25519 signature (base58)

Response

200 - application/json

Settings applied

status
enum<string>
Available options:
ok,
error
response
object