Binance Derivatives-trading-coin-futures Skill

Derivatives-trading-coin-futures 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

• recvWindow: (e.g., 5000)
• startTime: Timestamp in ms (e.g., 1623319461670)
• endTime: Timestamp in ms (e.g., 1641782889000)
• downloadId: get by download id api (e.g., 1)
• symbol:
• incomeType: "TRANSFER","WELCOME_BONUS", "FUNDING_FEE", "REALIZED_PNL", "COMMISSION", "INSURANCE_CLEAR", and "DELIVERED_SETTELMENT"
• startTime: (e.g., 1623319461670)
• endTime: (e.g., 1641782889000)
• page:
• limit: Default 100; max 1000 (e.g., 100)
• pair:
• symbol:
• pair: BTCUSD
• fromId: ID to get aggregate trades from INCLUSIVE. (e.g., 1)
• asset:
• orderId: (e.g., 1)
• orderId: (e.g., 1)
• countdownTime: countdown time, 1000 for 1 second. 0 to cancel the timer
• orderIdList: max length 10 e.g. [1234567,2345678]
• origClientOrderIdList: max length 10 e.g. ["my_id_1","my_id_2"], encode the double quotes. No space after comma.
• origClientOrderId: (e.g., 1)
• leverage: target initial leverage: int from 1 to 125
• dualSidePosition: "true": Hedge Mode; "false": One-way Mode
• type: 1: Add position margin,2: Reduce position margin
• amount: (e.g., 1.0)
• batchOrders: order list. Max 5 orders
• quantity: quantity measured by contract number, Cannot be sent with closePosition=true (e.g., 1.0)
• price: (e.g., 1.0)
• reduceOnly: "true" or "false". default "false". Cannot be sent in Hedge Mode; cannot be sent with closePosition=true(Close-All)
• newClientOrderId: A unique id among open orders. Automatically generated if not sent. Can only be string following the rule: ^[\.A-Z\:/a-z0-9_-]{1,36}$ (e.g., 1)
• stopPrice: Used with STOP/STOP_MARKET or TAKE_PROFIT/TAKE_PROFIT_MARKET orders. (e.g., 1.0)
• closePosition: true, false；Close-All,used with STOP_MARKET or TAKE_PROFIT_MARKET.
• activationPrice: Used with TRAILING_STOP_MARKET orders, default as the latest price(supporting different workingType) (e.g., 1.0)
• callbackRate: Used with TRAILING_STOP_MARKET orders, min 0.1, max 10 where 1 for 1% (e.g., 1.0)
• priceProtect: "TRUE" or "FALSE", default "FALSE". Used with STOP/STOP_MARKET or TAKE_PROFIT/TAKE_PROFIT_MARKET orders.
• batchOrders: order list. Max 5 orders
• marginAsset:

Enums

• contractType: PERPETUAL | CURRENT_QUARTER | NEXT_QUARTER | CURRENT_QUARTER_DELIVERING | NEXT_QUARTER_DELIVERING | PERPETUAL_DELIVERING
• period: 5m | 15m | 30m | 1h | 2h | 4h | 6h | 12h | 1d
• interval: 1m | 3m | 5m | 15m | 30m | 1h | 2h | 4h | 6h | 8h | 12h | 1d | 3d | 1w | 1M
• marginType: ISOLATED | CROSSED
• positionSide: BOTH | LONG | SHORT
• type: LIMIT | MARKET | STOP | STOP_MARKET | TAKE_PROFIT | TAKE_PROFIT_MARKET | TRAILING_STOP_MARKET
• side: BUY | SELL
• priceMatch: NONE | OPPONENT | OPPONENT_5 | OPPONENT_10 | OPPONENT_20 | QUEUE | QUEUE_5 | QUEUE_10 | QUEUE_20
• timeInForce: GTC | IOC | FOK | GTX
• workingType: MARK_PRICE | CONTRACT_PRICE
• newOrderRespType: ACK | RESULT
• selfTradePreventionMode: NONE | EXPIRE_TAKER | EXPIRE_BOTH | EXPIRE_MAKER
• autoCloseType: LIQUIDATION | ADL

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://dapi.binance.com
• Testnet: https://testnet.binancefuture.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
• Testnet: BINANCE_TESTNET_API_KEY and BINANCE_TESTNET_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" == *=* ]]