Exchange keys

The connector trades on your account through a key you create on the exchange and paste into the cabinet (onboarding step Exchange account, or Accounts → Add account later). One key is one account: give it a name, and it gets its own webhook URL. A sub-account is a separate account with its own key. The cabinet checks the key against the exchange before it saves anything; a wrong key, a bad secret or a missing futures permission comes back as the exchange's own error under the form.

The short version for every exchange:

• trading on futures: on, reading: on;
• withdrawals: off. Transfers: off. Always;
• no IP restriction (why: see below);
• ideally a sub-account used only for this.

Before you connect

• Use a sub-account if your exchange has them. The connector puts the futures account into hedge mode, and that applies to every position on it. Mixing manual trading and the connector on one account confuses both of you.
• Close everything on that futures account first. Binance only switches position mode when nothing is open. An account that's already in hedge mode is fine.
• Have enough margin for the full cascade of every symbol you'll run. See Risk presets.

Binance

USDT-M futures. In Account → API Management, create a key (system-generated is fine) and set:

Futures must be activated on the account before the key can get the futures permission. Paste the API key and the secret into the cabinet; the secret is shown by Binance only once.

Bybit

USDT perpetuals (linear contracts). In API Management, create a system-generated key with read and write access and:

• contract (derivatives) trading permissions for orders and positions: on;
• withdrawal and transfer permissions: off;
• no IP restriction.

The connector sets hedge mode per symbol on its first order there.

Hyperliquid

USDC perpetuals. Hyperliquid has no API key and secret; it uses an API wallet (an agent wallet) that can sign trades but can't withdraw or transfer.

1. Open app.hyperliquid.xyz → More → API.
2. Generate a new API wallet, give it a name, and copy its private key right away: it isn't shown again.
3. Authorize it with a signature from your main wallet (no transaction, no gas).
4. Note the expiry date. Named API wallets expire, up to about 180 days; put a reminder in your calendar and replace the key before it runs out.
5. In the cabinet enter your main wallet address (0x + 40 characters) and the API wallet's private key (64 characters).

Never paste your main wallet's private key anywhere. The connector doesn't need it and the cabinet doesn't ask for it.

On Hyperliquid there's one net position per symbol, so the strategy's long and short bots can't both hold the same symbol: the second open is refused. Only USDC pairs trade there.

Why no IP restriction

An IP whitelist is a good extra lock, and I'd use it if I could. The connector's outgoing IP address isn't fixed right now: it can change between deployments, and a whitelisted key would stop working without warning. So the protection is the permissions instead: a key that can't withdraw or transfer can, at worst, trade. A fixed IP is on the list; when it's there, these docs will say so.

Replacing or removing a key

• Replace keys (cabinet → Accounts, on the account's card) swaps the key for a new one of the same exchange account; the old one stops being used at once. A key of another account is refused: add it as a new account. Revoke the old key on the exchange afterwards.
• Remove deletes the account: its key and its webhook URL stop working at once, so delete the TradingView alerts that use the URL. Open positions stay on the exchange and keep their TP orders, with no one managing them. The trade log keeps the account's history under its name.
• Fastest stop of all: revoke the key on the exchange. Nothing can trade after that, whatever the connector does.

The connector stores keys encrypted and never displays them again, to you or to me.