Connect an exchange
Rejected keys
Why a key was refused or a connection disabled, and how to fix it.
| Message | Cause | Fix |
|---|---|---|
| This API key can withdraw funds | The key has withdrawal permission | Create a new key with withdrawals off. Editing the old key is not enough on every exchange |
| This API key can transfer funds between accounts | Binance universal or internal transfer is on | Turn off transfer permissions, or create a new key |
| This API key carries Wallet permissions | Bybit key with any Wallet permission | Create a key without Wallet permissions |
| Enable Futures / Contract trade permission | The market you chose is not enabled on the key | Enable trading for that market, or choose the other market |
| This API key is read-only; it needs trade permission | Read-only key | Create a key with trade permission |
| Could not read this key's permissions | The exchange did not answer clearly | Try again; if it persists, check the key and passphrase |
| No IP restriction on this key (warning) | The key works from any IP | Restrict it to the platform IPs shown on the connect page |
A connection was disabled. We re-check keys daily. If a key gains withdraw or transfer rights, the connection is disabled at once and trading stops; positions on the exchange are not touched. Create a new trade-only key and connect it again, or rotate the key on the connection page.
The exchange rejects the key (EXCHANGE_AUTH). The key was deleted or expired at the exchange, or the IP allowlist does not include
the platform IPs. Rotate the key from the connection page.