Get Sub-Account Position Leverage Multipliers
The master account uses this endpoint to query the position leverage of a specified sub-account on a given contract.
HTTP Request
- GET
/api/v1/private/position/leverage/subaccount
Required Permission: View Order Details (master-account API Key only)
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| subAccount | string | true | Sub-account name; can be obtained from the Query Sub-Account List endpoint |
| symbol | string | true | Contract name |
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| subAccount | string | Sub-account name |
| symbol | string | Contract name |
| positionType | int | Position type, 1 long 2 short |
| openType | int | Open type, 1: isolated, 2: cross |
| leverage | int | Leverage |
| maxLeverageView | int | Maximum leverage |
| currentMmr | decimal | Maintenance margin rate |
Notes
- The response structure is consistent with Get Position Leverage Multipliers, with additional
subAccountandsubUidfields to identify the sub-account. - Calling this endpoint with a sub-account API Key returns a permission error; the same applies when
subAccountdoes not belong to the current master account. - Returned items are grouped by
positionType(long/short). If the corresponding position is not open, the default leverage configuration for that contract is still returned.
Response
{
"success": true,
"code": 0,
"data": [
{
"subAccount": "mexc_sub_01",
"subUid": "49910511",
"symbol": "BTC_USDT",
"level": 6,
"maxVol": 4500000,
"mmr": 0.05,
"imr": 0.1,
"positionType": 1,
"openType": 1,
"leverage": 2,
"limitBySys": false,
"currentMmr": 0.001,
"maxLeverageView": 500
},
{
"subAccount": "mexc_sub_01",
"subUid": "49910511",
"symbol": "BTC_USDT",
"level": 6,
"maxVol": 4500000,
"mmr": 0.05,
"imr": 0.1,
"positionType": 2,
"openType": 1,
"leverage": 2,
"limitBySys": false,
"currentMmr": 0.001,
"maxLeverageView": 500
}
]
}