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

Endpoint	Description	Required	Optional	Authentication
`/dapi/v1/account` (GET)	Account Information (USER_DATA)	None	recvWindow	Yes
`/dapi/v1/balance` (GET)	Futures Account Balance (USER_DATA)	None	recvWindow	Yes
`/dapi/v1/positionSide/dual` (GET)	Get Current Position Mode(USER_DATA)	None	recvWindow	Yes
`/dapi/v1/positionSide/dual` (POST)	Change Position Mode(TRADE)	dualSidePosition	recvWindow	Yes
`/dapi/v1/order/asyn` (GET)	Get Download Id For Futures Order History (USER_DATA)	startTime, endTime	recvWindow	Yes
`/dapi/v1/trade/asyn` (GET)	Get Download Id For Futures Trade History (USER_DATA)	startTime, endTime	recvWindow	Yes
`/dapi/v1/income/asyn` (GET)	Get Download Id For Futures Transaction History(USER_DATA)	startTime, endTime	recvWindow	Yes
`/dapi/v1/order/asyn/id` (GET)	Get Futures Order History Download Link by Id (USER_DATA)	downloadId	recvWindow	Yes
`/dapi/v1/trade/asyn/id` (GET)	Get Futures Trade Download Link by Id(USER_DATA)	downloadId	recvWindow	Yes
`/dapi/v1/income/asyn/id` (GET)	Get Futures Transaction History Download Link by Id (USER_DATA)	downloadId	recvWindow	Yes
`/dapi/v1/income` (GET)	Get Income History(USER_DATA)	None	symbol, incomeType, startTime, endTime, page, limit, recvWindow	Yes
`/dapi/v1/leverageBracket` (GET)	Notional Bracket for Pair(USER_DATA)	None	pair, recvWindow	Yes
`/dapi/v2/leverageBracket` (GET)	Notional Bracket for Symbol(USER_DATA)	None	symbol, recvWindow	Yes
`/dapi/v1/commissionRate` (GET)	User Commission Rate (USER_DATA)	symbol	recvWindow	Yes
`/dapi/v1/ticker/24hr` (GET)	24hr Ticker Price Change Statistics	None	symbol, pair	No
`/futures/data/basis` (GET)	Basis	pair, contractType, period	limit, startTime, endTime	No
`/dapi/v1/time` (GET)	Check Server time	None	None	No
`/dapi/v1/aggTrades` (GET)	Compressed/Aggregate Trades List	symbol	fromId, startTime, endTime, limit	No
`/dapi/v1/continuousKlines` (GET)	Continuous Contract Kline/Candlestick Data	pair, contractType, interval	startTime, endTime, limit	No
`/dapi/v1/exchangeInfo` (GET)	Exchange Information	None	None	No
`/dapi/v1/fundingInfo` (GET)	Get Funding Rate Info	None	None	No
`/dapi/v1/fundingRate` (GET)	Get Funding Rate History of Perpetual Futures	symbol	startTime, endTime, limit	No
`/dapi/v1/constituents` (GET)	Query Index Price Constituents	symbol	None	No
`/dapi/v1/indexPriceKlines` (GET)	Index Price Kline/Candlestick Data	pair, interval	startTime, endTime, limit	No
`/dapi/v1/premiumIndex` (GET)	Index Price and Mark Price	None	symbol, pair	No
`/dapi/v1/klines` (GET)	Kline/Candlestick Data	symbol, interval	startTime, endTime, limit	No
`/futures/data/globalLongShortAccountRatio` (GET)	Long/Short Ratio	pair, period	limit, startTime, endTime	No
`/dapi/v1/markPriceKlines` (GET)	Mark Price Kline/Candlestick Data	symbol, interval	startTime, endTime, limit	No
`/dapi/v1/historicalTrades` (GET)	Old Trades Lookup(MARKET_DATA)	symbol	limit, fromId	No
`/futures/data/openInterestHist` (GET)	Open Interest Statistics	pair, contractType, period	limit, startTime, endTime	No
`/dapi/v1/openInterest` (GET)	Open Interest	symbol	None	No
`/dapi/v1/depth` (GET)	Order Book	symbol	limit	No
`/dapi/v1/premiumIndexKlines` (GET)	Premium index Kline Data	symbol, interval	startTime, endTime, limit	No
`/dapi/v1/trades` (GET)	Recent Trades List	symbol	limit	No
`/dapi/v1/ticker/bookTicker` (GET)	Symbol Order Book Ticker	None	symbol, pair	No
`/dapi/v1/ticker/price` (GET)	Symbol Price Ticker	None	symbol, pair	No
`/futures/data/takerBuySellVol` (GET)	Taker Buy/Sell Volume	pair, contractType, period	limit, startTime, endTime	No
`/dapi/v1/ping` (GET)	Test Connectivity	None	None	No
`/futures/data/topLongShortAccountRatio` (GET)	Top Trader Long/Short Ratio (Accounts)	symbol, period	limit, startTime, endTime	No
`/futures/data/topLongShortPositionRatio` (GET)	Top Trader Long/Short Ratio (Positions)	pair, period	limit, startTime, endTime	No
`/dapi/v1/pmAccountInfo` (GET)	Classic Portfolio Margin Account Information (USER_DATA)	asset	recvWindow	Yes
`/dapi/v1/userTrades` (GET)	Account Trade List (USER_DATA)	None	symbol, pair, orderId, startTime, endTime, fromId, limit, recvWindow	Yes
`/dapi/v1/allOrders` (GET)	All Orders (USER_DATA)	None	symbol, pair, orderId, startTime, endTime, limit, recvWindow	Yes
`/dapi/v1/countdownCancelAll` (POST)	Auto-Cancel All Open Orders (TRADE)	symbol, countdownTime	recvWindow	Yes
`/dapi/v1/allOpenOrders` (DELETE)	Cancel All Open Orders(TRADE)	symbol	recvWindow	Yes
`/dapi/v1/batchOrders` (DELETE)	Cancel Multiple Orders(TRADE)	symbol	orderIdList, origClientOrderIdList, recvWindow	Yes
`/dapi/v1/batchOrders` (PUT)	Modify Multiple Orders(TRADE)	batchOrders	recvWindow	Yes
`/dapi/v1/batchOrders` (POST)	Place Multiple Orders(TRADE)	batchOrders	recvWindow	Yes
`/dapi/v1/order` (DELETE)	Cancel Order (TRADE)	symbol	orderId, origClientOrderId, recvWindow	Yes
`/dapi/v1/order` (PUT)	Modify Order (TRADE)	symbol, side	orderId, origClientOrderId, quantity, price, priceMatch, recvWindow	Yes
`/dapi/v1/order` (POST)	New Order (TRADE)	symbol, side, type	positionSide, timeInForce, quantity, reduceOnly, price, newClientOrderId, stopPrice, closePosition, activationPrice, callbackRate, workingType, priceProtect, newOrderRespType, priceMatch, selfTradePreventionMode, recvWindow	Yes
`/dapi/v1/order` (GET)	Query Order (USER_DATA)	symbol	orderId, origClientOrderId, recvWindow	Yes
`/dapi/v1/leverage` (POST)	Change Initial Leverage (TRADE)	symbol, leverage	recvWindow	Yes
`/dapi/v1/marginType` (POST)	Change Margin Type (TRADE)	symbol, marginType	recvWindow	Yes
`/dapi/v1/openOrders` (GET)	Current All Open Orders (USER_DATA)	None	symbol, pair, recvWindow	Yes
`/dapi/v1/orderAmendment` (GET)	Get Order Modify History (USER_DATA)	symbol	orderId, origClientOrderId, startTime, endTime, limit, recvWindow	Yes
`/dapi/v1/positionMargin/history` (GET)	Get Position Margin Change History(TRADE)	symbol	type, startTime, endTime, limit, recvWindow	Yes
`/dapi/v1/positionMargin` (POST)	Modify Isolated Position Margin(TRADE)	symbol, amount, type	positionSide, recvWindow	Yes
`/dapi/v1/adlQuantile` (GET)	Position ADL Quantile Estimation(USER_DATA)	None	symbol, recvWindow	Yes
`/dapi/v1/positionRisk` (GET)	Position Information(USER_DATA)	None	marginAsset, pair, recvWindow	Yes
`/dapi/v1/openOrder` (GET)	Query Current Open Order(USER_DATA)	symbol	orderId, origClientOrderId, recvWindow	Yes
`/dapi/v1/forceOrders` (GET)	User's Force Orders(USER_DATA)	None	symbol, autoCloseType, startTime, endTime, limit, recvWindow	Yes
`/dapi/v1/listenKey` (DELETE)	Close User Data Stream(USER_STREAM)	None	None	No
`/dapi/v1/listenKey` (PUT)	Keepalive User Data Stream (USER_STREAM)	None	None	No
`/dapi/v1/listenKey` (POST)	Start User Data Stream (USER_STREAM)	None	None	No

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

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.

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:

bash

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).

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:

bash

# 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 -d= -f2-)
    SECRET_KEY=$(grep '^BINANCE_SECRET_KEY=' "$env_file" 2>/dev/null | cut -d= -f2-)
  else
    # Treat lines as raw values
    API_KEY="$line1"
    SECRET_KEY="$line2"
  fi
done

This file can be updated at any time without restarting OpenClaw, keys are read fresh on each invocation. Users can tell you the variables are now set or stored in a

.env

file, and you should re-read that file when they do.

Inline file

Sending a file where the content is in the following format:

bash

abc123...xyz
secret123...key

Never run
```
printenv
```
,
```
env
```
,
```
export
```
, or set without a specific variable name
Never run
```
grep
```
on
```
env
```
files without anchoring to a specific key ('
```
^VARNAME='
```
)
Never source a secrets file into the shell environment (
```
source .env
```
or
```
. .env
```
)
Only read credentials explicitly needed for the current task
Never echo or log raw credentials in output or replies
Never commit
```
TOOLS.md
```
to version control if it contains real credentials — add it to
```
.gitignore
```

Never Disclose API Key and Secret

Never disclose the location of the API key and secret file.

Never send the API key and secret to any website other than Mainnet and Testnet.

Never Display Full Secrets

When showing credentials to users:

API Key: Show first 5 + last 4 characters:
```
su1Qc...8akf
```
Secret Key: Always mask, show only last 5:
```
***...aws1
```

Example response when asked for credentials: Account: main API Key: su1Qc...8akf Secret: ***...aws1 Environment: Mainnet

Listing Accounts

When listing accounts, show names and environment only — never keys: Binance Accounts:

main (Mainnet/Testnet)
testnet-dev (Testnet)
futures-keys (Mainnet)

Transactions in Mainnet

When performing transactions in mainnet, always confirm with the user before proceeding by asking them to write "CONFIRM" to proceed.

Binance Accounts

main

API Key: your_mainnet_api_key
Secret: your_mainnet_secret
Testnet: false

testnet-dev

API Key: your_testnet_api_key
Secret: your_testnet_secret
Testnet: true

TOOLS.md Structure

bash

## Binance Accounts

### main
- API Key: abc123...xyz
- Secret: secret123...key
- Testnet: false
- Description: Primary trading account

### testnet-dev
- API Key: test456...abc
- Secret: testsecret...xyz
- Testnet: true
- Description: Development/testing

### futures-keys
- API Key: futures789...def
- Secret: futuressecret...uvw
- Testnet: false
- Description: Futures trading account

Agent Behavior

Credentials requested: Mask secrets (show last 5 chars only)
Listing accounts: Show names and environment, never keys
Account selection: Ask if ambiguous, default to main
When doing a transaction in mainnet, confirm with user before by asking to write "CONFIRM" to proceed
New credentials: Prompt for name, environment, signing mode
When a request requires signing, if the request isn't an order and the API keys aren't described as
```
mainnet
```
or
```
testnet
```
keys, try to make request to the different base urls and see if it works, without asking the user. If it works, store the keys with the corresponding environment.

Adding New Accounts

When user provides new credentials by Inline file or message:

Ask for account name
Ask: Mainnet, Testnet
Store in
```
TOOLS.md
```
with masked display confirmation

Signing Requests

For trading endpoints that require a signature:

Detect key type first, inspect the secret key format before signing.
Build query string with all parameters, including the timestamp (Unix ms).
Percent-encode the parameters using UTF-8 according to RFC 3986.
Sign query string with secretKey using HMAC SHA256, RSA, or Ed25519 (depending on the account configuration).
Append signature to query string.
Include
```
X-MBX-APIKEY
```
header.

Otherwise, do not perform steps 4–6.

New Client Order ID

For endpoints that include the

newClientOrderId

parameter, the value must always start with

agent-

. If the parameter is not provided,

agent-

followed by 18 random alphanumeric characters will be generated automatically. If a value is provided, it will be prefixed with

agent-

Example:

agent-1a2b3c4d5e6f7g8h9i

User Agent Header

Include

User-Agent

header with the following string:

binance-derivatives-trading-coin-futures/1.1.0 (Skill)

See

references/authentication.md

for implementation details.

derivatives-trading-coin-futures

NPX Install

SKILL.md Content

Binance Derivatives-trading-coin-futures Skill

Quick Reference

Parameters

Common Parameters

Enums

Authentication

Security

Share Credentials

Never Disclose API Key and Secret

Never Display Full Secrets

Listing Accounts

Transactions in Mainnet

Binance Accounts

main

testnet-dev

TOOLS.md Structure

Agent Behavior

Adding New Accounts

Signing Requests

New Client Order ID

User Agent Header