Change Initial Leverage
Type: TRADE
Weight: 1
POST /fapi/v1/leverage
Set the leverage used for subsequent orders on a symbol.
Request
POST /fapi/v1/leverage?timestamp=<ms>&signature=<hex>
Content-Type: application/json
{ "symbol": "BTCUSDT", "leverage": 10 }
Body params
| Name | Type | Required | Notes |
|---|---|---|---|
symbol | string | yes | |
leverage | int or string | yes | 1 ≤ leverage ≤ market max; 10 and "10" both accepted. |
Response — 200
{ "leverage": 10, "maxNotionalValue": "10000000", "symbol": "BTCUSDT" }
The value is persisted per (user, symbol) and read by every subsequent POST /fapi/v1/order, where it is additionally clamped to the market's current maximum (protects against a market max being lowered after you set a higher value). Leverage is a standing setting, not a per-order parameter. This endpoint does not switch margin mode.
Errors
| HTTP | code | msg |
|---|---|---|
400 | -1121 | Invalid symbol. |
400 | -4028 | Leverage outside [1, market max]. |
Authentication failures (INVALID_API_KEY, API_KEY_DISABLED, IP_NOT_ALLOWED, SIGNATURE_INVALID) apply to every signed endpoint and use Sparky's {"success":false,"error":{...}} envelope; see Error Codes.