> ## Documentation Index
> Fetch the complete documentation index at: https://docs.polymarket.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Update Leverage
> Perps WebSocket leverage updates.
## AsyncAPI
````yaml asyncapi-perps.json updateLeverage
id: updateLeverage
title: Update Leverage
description: >
Each setting resolves independently: explicit per-instrument setting, then
exchange-managed account-group default, then instrument maximum leverage and
isolated margin. Group leverage is capped at the instrument maximum; a group
cross default resolves to isolated on isolated-only instruments. Group
defaults
apply to new listings and never overwrite explicit settings.
Updating leverage sets both values explicitly. GET /v1/account/config returns
the resolved values. Submit the current resolved pair to preserve it against
later group changes. Leverage bounds and BLP locks also apply to unchanged
values.
Set leverage and margin type for an instrument.
Requires proxy signature, see [proxy signing](/http/signing#2-proxy-signing).
Action Weight: **1**
servers:
- id: production
protocol: wss
host: ws.perpetuals.polymarket.com
bindings: []
variables: []
address: /v1/ws
parameters: []
bindings: []
operations:
- &ref_1
id: UpdateLeverageSend
title: Update leverage send
description: Update leverage
type: receive
messages:
- &ref_3
id: Request
contentType: application/json
payload:
- name: Update Leverage Request
description: Client submits a signed leverage update request
type: object
properties:
- name: id
type: integer
description: Correlation ID for request-response matching
required: false
- name: req
type: string
description: Request type
enumValues:
- post
- sub
- unsub
required: true
- name: op
type: object
required: true
properties:
- name: type
type: string
enumValues:
- updateLeverage
required: true
- name: args
type: object
required: true
properties:
- name: iid
type: integer
description: Instrument ID
required: true
- name: lev
type: integer
description: Leverage
required: true
- name: cross
type: boolean
description: Whether to use cross margin mode
required: true
- name: sig
type: string
description: Signature in hex format
required: true
- name: salt
type: integer
description: Salt
required: true
- name: ts
type: integer
description: >-
Request timestamp. Unix milliseconds for most operations; Unix
seconds for withdrawals (must match the on-chain EIP-712
struct verified against block.timestamp).
required: true
headers: []
jsonPayloadSchema:
type: object
title: Base Request
properties:
id:
type: integer
description: Correlation ID for request-response matching
x-parser-schema-id:
req:
type: string
description: Request type
enum:
- post
- sub
- unsub
x-parser-schema-id:
op:
type: object
required:
- type
- args
properties:
type:
type: string
enum:
- updateLeverage
x-parser-schema-id:
args:
type: object
required:
- iid
- lev
- cross
properties:
iid:
type: integer
description: Instrument ID
example: 1
x-parser-schema-id:
lev:
type: integer
description: Leverage
example: 10
x-parser-schema-id:
cross:
type: boolean
description: Whether to use cross margin mode
x-parser-schema-id:
x-parser-schema-id:
x-parser-schema-id:
sig:
type: string
description: Signature in hex format
example: 0x1234567890...
x-parser-schema-id:
salt:
type: integer
description: Salt
example: 1234567890
x-parser-schema-id:
ts:
type: integer
description: >-
Request timestamp. Unix milliseconds for most operations; Unix
seconds for withdrawals (must match the on-chain EIP-712 struct
verified against block.timestamp).
example: 1767225600000
x-parser-schema-id:
required:
- req
- op
- sig
- salt
- ts
x-parser-schema-id:
title: Update Leverage Request
description: Client submits a signed leverage update request
example: |-
{
"req": "post",
"op": {
"type": "updateLeverage",
"args": {
"iid": 1,
"lev": 10
}
},
"sig": "0x1234567890...",
"salt": 1234567890,
"ts": 1767225600000
}
bindings: []
extensions:
- id: x-parser-unique-object-id
value: Request
bindings: []
extensions: &ref_0
- id: x-parser-unique-object-id
value: updateLeverage
- &ref_2
id: UpdateLeverageReceive
title: Update leverage receive
description: Update leverage response
type: send
messages:
- &ref_4
id: Response
contentType: application/json
payload:
- name: Update Leverage Response
description: Server responds with leverage update result
type: object
properties:
- name: id
type: integer
description: Correlation ID for request-response matching
required: false
- name: data
type: object
required: true
properties:
- name: status
type: string
enumValues:
- ok
required: true
- name: status
type: string
enumValues:
- err
required: true
- name: error
type: string
description: >-
Error identifier. For domain rejections and transport
errors (`401`/`404`/`429`/`500`) this is a stable,
machine-readable snake_case identifier that is part of the
API contract and safe to branch on, e.g.
`insufficient_margin`, `insufficient_balance`,
`order_not_found`, `reduce_only_invalid`,
`price_outside_bounds`, `position_not_found`,
`position_exists`, `open_orders_exist`,
`invalid_margin_mode`, `invalid_margin_amount`,
`margin_below_required_initial`, `account_liquidating`,
`unauthorized`, `not_found`. For `400` it is a
human-readable validation detail whose wording may change.
See the Error handling guide for the domain identifiers.
(Post-only / Fill-or-Kill outcomes are order statuses such
as `post_only_rejected`, not rejections.)
required: true
headers: []
jsonPayloadSchema:
type: object
title: Base Response
properties:
id:
type: integer
description: Correlation ID for request-response matching
x-parser-schema-id:
data:
oneOf:
- type: object
required:
- status
properties:
status:
type: string
enum:
- ok
x-parser-schema-id:
x-parser-schema-id:
- type: object
required:
- status
- error
properties:
status:
type: string
enum:
- err
x-parser-schema-id:
error:
type: string
description: >-
Error identifier. For domain rejections and transport
errors (`401`/`404`/`429`/`500`) this is a stable,
machine-readable snake_case identifier that is part of
the API contract and safe to branch on, e.g.
`insufficient_margin`, `insufficient_balance`,
`order_not_found`, `reduce_only_invalid`,
`price_outside_bounds`, `position_not_found`,
`position_exists`, `open_orders_exist`,
`invalid_margin_mode`, `invalid_margin_amount`,
`margin_below_required_initial`, `account_liquidating`,
`unauthorized`, `not_found`. For `400` it is a
human-readable validation detail whose wording may
change. See the Error handling guide for the domain
identifiers. (Post-only / Fill-or-Kill outcomes are
order statuses such as `post_only_rejected`, not
rejections.)
example: insufficient_margin
x-parser-schema-id:
x-parser-schema-id:
x-parser-schema-id:
required:
- data
x-parser-schema-id:
title: Update Leverage Response
description: Server responds with leverage update result
example: |-
{
"id": 6,
"data": {
"status": "ok"
}
}
bindings: []
extensions:
- id: x-parser-unique-object-id
value: Response
bindings: []
extensions: *ref_0
sendOperations:
- *ref_1
receiveOperations:
- *ref_2
sendMessages:
- *ref_3
receiveMessages:
- *ref_4
extensions:
- id: x-parser-unique-object-id
value: updateLeverage
securitySchemes: []
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.