Docs·Web App·API Connect

API Connect — overview

Connect your exchange account so the platform can read your balances, place orders on your behalf, and feed positions to autotrade. We require trade-only keys (no withdrawal), use IP whitelisting where supported, and never custody funds.

API Connect is how you authorise the platform to read your exchange account and place orders on your behalf. You generate an API key on the exchange, paste it on our API Connect page, and the platform validates the key + permissions immediately. Once connected, your balances appear in the Bottom panel → Assets, your orders / fills surface in Open Orders / Trade History, and Auto Trade can execute signals via the key.

Security model: we require trade-only keys (withdraw permission must be off), use IP whitelisting where the exchange supports it, and never custody funds. Your private key stays on the exchange — we only hold the API key + secret, which can only do what their permissions allow.

API Connect page

Supported exchanges

ExchangeWhat's supported
Binance Futures (USDⓈ-M)Spot + USDⓈ-M perpetual. The canonical Auto Trade execution venue.
Binance SpotRead-only mode supported; full trade-execution mode planned.
BybitRead-only mode (perpetual + spot); execution planned.
OKXRead-only mode; execution planned.
BitgetRead-only mode; execution planned.
KucoinRead-only mode; execution planned.

Today, Binance Futures is the only venue that supports execution via Auto Trade. The other venues you can connect for monitoring (balance + positions surface across the app) but autotrade won't route to them yet. The roadmap is to add execution per-venue based on demand.

Key permissions required

For each exchange, the minimum permission set:

PermissionRequired for
Read accountBalance display, positions display.
Read trade historyTrade History tab.
Read ordersOpen Orders tab.
Trade (spot / futures)Placing orders from chart, quick-trade, autotrade.
WithdrawMUST BE OFF. We refuse keys with withdraw enabled.
TransferMUST BE OFF.
MarginOptional; only needed for margin trading.

The Binance setup page walks you through generating a key with the right permissions — see API Connect — Binance.

What gets stored on our side

Encrypted at rest:

  • API key (the public identifier).
  • API secret (the signing secret).
  • IP whitelist value (if set on the exchange side).
  • The exchange + account label you choose.

We do NOT store:

  • Your exchange password.
  • Your 2FA codes.
  • Your withdraw whitelist.

Multi-account

Connect multiple accounts per exchange — useful for separating personal / IB sub-account / a manual-only sub. Each connected account gets a row in the API Connect page with its own:

  • Label (your-chosen name).
  • Status (Connected / Re-auth needed / Error).
  • Permission summary.
  • Last sync timestamp.
  • Disconnect button.

Auto Trade picks one account as the active execution account; the others are read-only mirrors in the balance / positions panels.

Health check

The platform pings each connected key every 60 seconds. On a failed ping:

  1. The card flips to Error with the exchange's error message.
  2. A red banner appears in the top toolbar.
  3. Auto Trade pauses for that account.
  4. If the failure persists, a push / Telegram trade alert fires (see Trade alerts).

Self-heal — most transient errors (rate-limited, brief 5xx) recover on the next ping.

Pages

PageWhat it covers
Binance Futures connectStep-by-step Binance Futures key generation + paste flow.
IP whitelistWhy and how to add our server IPs to your key's whitelist.

Common pitfalls

  • Pasted a key with withdraw permission — we refuse it at validation. Regenerate the key with withdraw OFF.
  • Generated the key under "Spot" tab instead of "Futures" tab on Binance — same key string, different permission scope; futures orders will fail. Re-generate under Futures.
  • Stored key on a public computer — keys are encrypted on our side but a fresh tab + signed-in browser exposes the API Connect page. Always sign out on shared machines.

What's next