REST reference / Trading and account

Change position mode

POST/fapi/v1/positionSide/dual
Signed requestTrading permissionWeight 1

Overview

Retain one-way mode, hedge mode is rejected

Send X-MBX-APIKEY and an HMAC-SHA256 signature. Sign requests in your own client. Authentication guide

Behavior and request rules

Requires X-MBX-APIKEY and per-request HMAC-SHA256. Send timestamp (milliseconds), optional recvWindow (default 5000, maximum 60000), and signature. Sign the exact raw query followed by the exact raw body, with NO inserted ampersand, excluding signature. Signature must be last in query or body. Query values take precedence over body values; the first duplicate in each location wins. Values are not percent-decoded. Timestamp must be less than serverTime + 1000 and serverTime - timestamp <= recvWindow. The API-key authorization field alone does not sign requests.

Parameters may be in query, raw urlencoded body, or split across both. Required fields apply to the merged parameters, not independently to each location. Query parameters are marked optional to represent this alternative. GET bodies work at the server but many HTTP clients and proxies cannot send them; use query parameters for portable GET requests. Send the exact bytes you signed, without form re-encoding.

TRADE permission is required.

Parameters

Required fields apply across query and form body. Query values take precedence. The examples use query parameters only.

dualSidePositionstringrequired

String parameter. Only false succeeds; true returns -4061.

Constraints
type
"string"
enum
["false","true"]
timestampintegerrequired

Client epoch milliseconds checked against the receive window.

Constraints
type
"integer"
format
"int64"
recvWindowintegeroptional

Receive window in milliseconds.

Constraints
type
"integer"
minimum
1
maximum
60000
default
5000
signaturestringrequired

HMAC-SHA256 of exact raw query + body excluding signature; final parameter in query or body.

Constraints
type
"string"
pattern
"^[0-9a-fA-F]{64}$"
Conditional and combined requirements

These constraints apply after query and body parameters are combined. Field descriptions above explain conditions such as the LIMIT price requirement.

Combined parameter schema
{
  "properties": {
    "dualSidePosition": {
      "description": "String parameter. Only false succeeds; true returns -4061.",
      "enum": [
        "false",
        "true"
      ],
      "type": "string"
    },
    "recvWindow": {
      "default": 5000,
      "description": "Receive window in milliseconds.",
      "maximum": 60000,
      "minimum": 1,
      "type": "integer"
    },
    "signature": {
      "description": "HMAC-SHA256 of exact raw query + body excluding signature; final parameter in query or body.",
      "pattern": "^[0-9a-fA-F]{64}$",
      "type": "string"
    },
    "timestamp": {
      "description": "Client epoch milliseconds checked against the receive window.",
      "format": "int64",
      "type": "integer"
    }
  },
  "required": [
    "dualSidePosition",
    "timestamp",
    "signature"
  ],
  "type": "object"
}
Form body schema

Parameters may be in query, raw urlencoded body, or split across both. Required fields apply to the merged parameters, not independently to each location. Query parameters are marked optional to represent this alternative. GET bodies work at the server but many HTTP clients and proxies cannot send them; use query parameters for portable GET requests. Send the exact bytes you signed, without form re-encoding.

Form body schema
{
  "application/x-www-form-urlencoded": {
    "schema": {
      "properties": {
        "dualSidePosition": {
          "description": "String parameter. Only false succeeds; true returns -4061.",
          "enum": [
            "false",
            "true"
          ],
          "type": "string"
        },
        "recvWindow": {
          "default": 5000,
          "description": "Receive window in milliseconds.",
          "maximum": 60000,
          "minimum": 1,
          "type": "integer"
        },
        "signature": {
          "description": "HMAC-SHA256 of exact raw query + body excluding signature; final parameter in query or body.",
          "pattern": "^[0-9a-fA-F]{64}$",
          "type": "string"
        },
        "timestamp": {
          "description": "Client epoch milliseconds checked against the receive window.",
          "format": "int64",
          "type": "integer"
        }
      },
      "type": "object"
    }
  }
}

Responses

Success

codeintegerrequired
type
"integer"
format
"int64"
msgstringrequired
type
"string"
type
"object"
additionalProperties
false
Response headers
X-DP-ACCOUNT-USED-WEIGHT-1M

Per-verified-Trading-Account admitted weight when authenticated.

X-MBX-USED-WEIGHT-1M

Per-IP admitted request weight in the current minute. Requests admitted by the limiter count even if authentication or validation later fails.

Raw response schema
Response schema
{
  "$ref": "#/components/schemas/Message"
}
Errors, limits and retry behavior