Binance Sub-account Skill

Sub-account request on Binance using authenticated API endpoints. Requires API key and secret key for certain endpoints. Return the result in JSON format.

Quick Reference

Parameters

Common Parameters

• subAccountString: Please input a string. We will create a virtual email using that string for you to register
• recvWindow: (e.g., 5000)
• email: Sub-account email (e.g., [email protected])
• futuresType: 1:USDT-margined Futures，2: Coin-margined Futures
• email: Managed sub-account email
• isFreeze: true or false
• page: Default value: 1 (e.g., 1)
• limit: Default value: 1, Max value: 200 (e.g., 1)
• subAccountApiKey:
• status: IP Restriction status. 1 = IP Unrestricted. 2 = Restrict access to trusted IPs only.
• ipAddress: Insert static IP in batch, separated by commas.
• ipAddress: IPs to be deleted. Can be added in batches, separated by commas
• asset:
• amount: (e.g., 1.0)
• type: 1: transfer from subaccount's spot account to margin account 2: transfer from subaccount's margin account to its spot account
• symbol:
• startTime: (e.g., 1623319461670)
• endTime: (e.g., 1641782889000)
• page: Page
• row:
• coin:
• network: networks can be found in GET /sapi/v1/capital/deposit/address
• amount: (e.g., 1.0)
• coin:
• status: 0(0:pending,6: credited but cannot withdraw,7:Wrong Deposit,8:Waiting User confirm,1:success)
• offset: default:0
• txId: (e.g., 1)
• limit: Limit (Max: 500)
• fromUserEmail:
• toUserEmail:
• productType: Only support UM
• orderArgs: Max 10 positions supported. When input request parameter,orderArgs.symbol should be STRING, orderArgs.quantity should be BIGDECIMAL, and orderArgs.positionSide should be STRING, positionSide support BOTH,LONG and SHORT. Each entry should be like orderArgs[0].symbol=BTCUSDT,orderArgs[0].quantity=0.001,orderArgs[0].positionSide=BOTH. Example of the request parameter array: orderArgs[0].symbol=BTCUSDT orderArgs[0].quantity=0.001 orderArgs[0].positionSide=BOTH orderArgs[1].symbol=ETHUSDT orderArgs[1].quantity=0.01 orderArgs[1].positionSide=BOTH
• fromEmail:
• toEmail:
• size: default 10, max 20 (e.g., 10)
• clientTranId: (e.g., 1)
• fromEmail:
• toEmail:
• asset: If not sent, result of all assets will be returned
• type: 1: transfer in, 2: transfer out
• returnFailHistory: Default False, return PROCESS and SUCCESS status history; If True,return PROCESS and SUCCESS and FAILURE status history
• fromAccountType: "SPOT","USDT_FUTURE","COIN_FUTURE","MARGIN"(Cross),"ISOLATED_MARGIN"
• toAccountType: "SPOT","USDT_FUTURE","COIN_FUTURE","MARGIN"(Cross),"ISOLATED_MARGIN"
• symbol: Only supported under ISOLATED_MARGIN type
• startTime: Start Time (e.g., 1623319461670)
• endTime: End Time (The start time and end time interval cannot exceed half a year) (e.g., 1641782889000)
• transfers: Transfer Direction (FROM/TO)
• transferFunctionAccountType: Transfer function account type (SPOT/MARGIN/ISOLATED_MARGIN/USDT_FUTURE/COIN_FUTURE)
• accountType: No input or input "MARGIN" to get Cross Margin account details. Input "ISOLATED_MARGIN" to get Isolated Margin account details.
• type: "SPOT", "MARGIN"（cross）, "FUTURES"（UM）
• transferDate: Withdrawals is automatically occur on the transfer date(UTC0). If a date is not selected, the withdrawal occurs right now

Authentication

For endpoints that require authentication, you will need to provide Binance API credentials. Required credentials:

• apiKey: Your Binance API key (for header)
• secretKey: Your Binance API secret (for signing)

Base URLs:

• Mainnet: https://api.binance.com

Security

Share Credentials

Users can provide Binance API credentials in different ways. The agent will try to retrieve automatically with the two first ways the credentials, but users can also explicitly tell the agent that they have set the credentials or stored them in a .env file, and the agent should re-read that file when they do. The agent can also make http requests with the two first methods without user confirmation.

1. Environment variables

Search for the following specific variables only (never dump the full environment):

Authorized environment variables

• Mainnet: BINANCE_API_KEY and BINANCE_SECRET_KEY

Read and use in a single exec call so the raw key never enters the agent's context:

KEY="$BINANCE_API_KEY"
SECRET="$BINANCE_SECRET_KEY"

response=$(curl -s -X GET "$URL" \
  -H "X-MBX-APIKEY: $KEY" \
  --data-urlencode "param1=value1")

echo "$response"

Environment variables must be set before OpenClaw starts. They are inherited at process startup and cannot be injected into a running instance. If you need to add or update credentials without restarting, use a secrets file (see option 2).

2. Secrets file (.env)

Check ~/.openclaw/secrets.env , ~/.env, or a .env file in the workspace. Read individual keys with grep, never source the full file:

# Try all credential locations in order
API_KEY=$(grep '^BINANCE_API_KEY=' ~/.openclaw/secrets.env 2>/dev/null | cut -d= -f2-)
SECRET_KEY=$(grep '^BINANCE_SECRET_KEY=' ~/.openclaw/secrets.env 2>/dev/null | cut -d= -f2-)

# Fallback: search .env in known directories (KEY=VALUE then raw line format)
for dir in ~/.openclaw ~; do
  [ -n "$API_KEY" ] && break
  env_file="$dir/.env"
  [ -f "$env_file" ] || continue

  # Read first two lines
  line1=$(sed -n '1p' "$env_file")
  line2=$(sed -n '2p' "$env_file")

  # Check if lines contain '=' indicating KEY=VALUE format
  if [[ "$line1" == *=* && "$line2" == *=* ]]; then
    API_KEY=$(grep '^BINANCE_API_KEY=' "$env_file" 2>/dev/null | cut