Set leverage
POSTπ Trading
Updates the leverage, margin mode, and position mode for the given symbol.
Request Parametersβ
| Name | Type | Required | Description |
|---|---|---|---|
| symbol | String | Yes | Trading symbol to update (e.g., BTC-PERP). |
| leverage | Double | Yes | Target leverage multiplier to apply. |
| positionMode | String | No | Position mode: ONE_WAY (single net position per symbol) or HEDGE (separate long and short positions). Defaults to ONE_WAY when omitted. |
| positionDirection | String | No | Position direction (LONG or SHORT). Used together with HEDGE position mode to identify which side to update when positionId is not supplied. |
| marginMode | String | No | Margin mode to apply: CROSS or ISOLATED. |
| positionId | String | No | Existing position identifier to update. Optional; disambiguates the target position in hedge mode. |
Response Contentβ
| Name | Type | Description |
|---|---|---|
| symbol | String | Trading symbol whose leverage was updated. |
| timestamp | Long | Server processing time, Unix timestamp in milliseconds. |
| status | Integer | Result status code (0 indicates success; non-zero indicates failure). |
| type | Integer | Result type code returned by the trading system. |
| message | String | Human-readable status message; typically populated on failure. |
example
POST
https://api.btse.com/futures/api/v3/trade/leverageRequest (default)
{
"symbol": "BTC-PERP",
"leverage": 10
}
Response (default)
{
"symbol": "BTC-PERP",
"timestamp": 1784882344185,
"status": 20,
"type": 93,
"message": "Leverage changed successfully to isolated mode, leverage: 10.0"
}