Docs·Web App·API Connect

Connect Binance Futures

Step-by-step Binance Futures API key generation with trade-only permission, paste flow on our side, and the validation outcomes. Includes the One-Way Mode prerequisite for Auto Trade and the IP whitelist call-out.

This page walks you through generating a Binance Futures API key with the correct permissions and pasting it on our API Connect page. Plan ~5 minutes. You need an existing Binance account; if you don't have one, sign up directly at binance.com — the autotrade flow works on any Binance Futures account.

Binance API management

Before you start

PrerequisiteCheck
Binance account verified to Tier 1 (KYC level 1)Required by Binance to create API keys.
Binance Futures account enabled (one-time form)Required to trade futures. Done under Futures menu the first time.
2FA enabled on your Binance accountRequired by Binance to create / edit keys.
Binance Futures in One-Way ModeRequired for Auto Trade. See Hedge mode notes.

Step 1 — Create the key on Binance

  1. Sign in to binance.com.
  2. Top-right menu → AccountAPI Management.
  3. Click Create API.
  4. Pick System generated (not the third-party HMAC option).
  5. Name the key — mrD-Indicators (so you remember what it's for).
  6. Pass 2FA.
  7. Binance shows the API Key and Secret Key strings — copy both. ⚠ The secret is shown ONCE; if you lose it, you have to delete the key and create a new one.

Step 2 — Set permissions

On the just-created key's row, click Edit restrictions:

PermissionSet to
Enable ReadingON
Enable Spot & Margin TradingOFF (unless you also use Spot)
Enable FuturesON
Permits Universal TransferOFF
Enable WithdrawalsOFF — must be off, we refuse keys with this on
Enable Symbol White ListOff (or restrict to the symbols you care about — affects autotrade range)

Save. Pass 2FA again.

On the same Edit page:

  • Click Restrict access to trusted IPs only.
  • Paste our server IPs (see IP whitelist for the exact list).
  • Save. Pass 2FA.

Skipping IP whitelist is fine for testing but strongly recommended for live use.

Step 4 — Paste on our side

  1. Open our API Connect page.
  2. Click + ConnectBinance Futures.
  3. Paste API Key and Secret Key.
  4. (Optional) Label the connection (e.g. "Main account").
  5. Click Validate.
  6. The validation runs immediately and reports one of:
OutcomeMeaning
ConnectedPermissions are correct; key is usable.
Withdrawal enabled — please disableWithdraw permission is on; we refuse. Go back to Binance and disable it.
Missing Futures permissionKey has Read but not Futures Trade. Re-enable on Binance.
IP not whitelistedOur server IP is not on your whitelist. Add it on Binance side.
Invalid signatureSecret pasted wrong (extra space, partial). Re-paste.

Step 5 — Verify in the app

After Connected, check:

If any of these is empty when you expect data, hit Refresh on the API Connect card.

Renewing / rotating the key

Binance keys don't expire by default, but rotating periodically is good hygiene:

  1. Create a new key with the same permissions on Binance.
  2. Paste it on our API Connect page (a second card appears).
  3. Verify the new card is Connected.
  4. Delete the old card on our side.
  5. Delete the old key on Binance.

Rotation should take < 5 minutes if you've done it once.

Disconnecting

API Connect card → Disconnect:

  • Removes the key from our storage immediately.
  • Open positions / orders remain on Binance — we don't touch them.
  • Auto Trade pauses for that account.
  • Re-connecting later restores everything (positions reappear, autotrade resumes if you flip LIVE).

Common pitfalls

  • Secret lost — Binance only shows once. Delete the key and create new.
  • Pasted master account UID instead of sub-account UID — wrong account links; rebates / autotrade misroute. Use the sub-account's own UID + key.
  • Validation passes but balance shows 0 — sometimes Binance lags on sub-account creation; wait a few minutes and refresh.
  • "IP not whitelisted" despite adding IPs — Binance whitelist propagation can take 5-10 min; wait then retry.

What's next