Adding Exchange API Keys
Create a trading-only API key on your exchange and store it with /secrets action:set.
Your API key lives on your own bot instance, encrypted at rest. It's never sent to any Ionide-operated service. Jump to the exchange on your license:
| Exchange | Passphrase required | Spot/futures keys |
|---|---|---|
Bitget | Yes | One key covers both |
MEXC | No | One key covers both |
OKX | Yes | One key covers both |
Kraken | No | Separate keys |
Gate.io | No | One key covers both |
Binance | No | One key covers both |
The rule: trading yes, withdrawals never
Ionide only needs trading permissions to place spot and futures orders. It never needs, and will never ask for, withdrawal permissions. If the exchange's key form has a withdrawal toggle, leave it off.
Bitget
- Go to API Management in your
Bitget account settings. - Create a new key and enable Spot Trading and Futures Trading permissions.
- Leave Withdraw unchecked.
Bitget also requires a passphrase you set when creating the key. Keep it, you'll need it
below.
Screenshot/video walkthrough of creating a
Bitget API key: coming soon.
MEXC
- Go to API Management in your
MEXC account settings. - Create a key and enable Spot Trading and/or Futures Trading, matching what you plan to run.
- Leave Withdraw unchecked.
- One key/secret pair covers both spot and futures — no passphrase required.
Screenshot/video walkthrough of creating a
MEXC API key: coming soon.
OKX
- Go to API Management in your
OKX account settings (use the site matching where your
account is registered: global or Europe). - Create a new key and enable Trade permissions.
- Leave Withdraw unchecked.
OKX also requires a passphrase you set when creating the key. Keep it, you'll need it below.
Screenshot/video walkthrough of creating an
OKX API key: coming soon.
Kraken
- Go to API Management in your
Kraken account settings. - Create a key and enable Query Funds, Query Open Orders & Trades, and Create & Modify Orders for spot and/or futures, matching what you plan to run.
- Leave any withdrawal/transfer permission unchecked.
Kraken's spot and futures API keys are separate, so you'll store them separately with
/secrets action:set(see below).
Screenshot/video walkthrough of creating a
Kraken API key: coming soon.
Gate.io
- Go to API Management in your
Gate.io account settings. - Create a key and enable Spot Trading and Futures Trading permissions.
- Leave Withdraw unchecked.
- One key/secret pair covers both spot and futures — no passphrase required.
Screenshot/video walkthrough of creating a
Gate.io API key: coming soon.
Binance
- Go to API Management in your
Binance account settings. - Create a key and enable Spot & Margin Trading and Futures permissions.
- Leave Withdrawals unchecked.
- One key/secret pair covers both spot and USDT-M futures — no passphrase required. Demo/testnet
keys come from
Binance Demo Trading; Ionide detects their environment automatically.
Screenshot/video walkthrough of creating a
Binance API key: coming soon.
Storing the key in Discord
Run /secrets action:set in your command center channel and choose the exchange:
bitget: needs API key, secret, and passphrase.mexc: needs API key and secret (no passphrase).okx/okx-europe: needs API key, secret, and passphrase.kraken-spot/kraken-futures: needs API key and secret (no passphrase).gateio: needs API key and secret (no passphrase).binance: needs API key and secret (no passphrase).
The bot encrypts what you enter and stores it locally. Values are never echoed back, not even to
you. Check what's configured with /secrets action:status, and verify a key actually works (including
confirming it has no withdrawal permission) with /secrets action:test.
Testnet and demo keys
Don't select or configure a testnet switch. Enter the key from the account you intend to use;
Ionide probes it during setup and automatically classifies it as testnet/demo or live. Check the
result with /secrets action:status. Use /secrets action:test after rotating a key or if its
environment looks wrong.
IP allowlists and rotation reminders
If your host has a stable public outbound IP address, add it to the exchange key's IP allowlist.
This is strongly recommended. If you cannot use an allowlist — for example, your host has a dynamic
home IP — some exchanges automatically expire unrestricted API keys. Ionide sends every bot owner a
one-time Discord reminder before the conservative estimated expiry date and shows the same warning
in /secrets action:status. Rotate the key with /secrets action:set before it stops working.
The date is an estimate from each exchange's typical no-IP-allowlist policy, not a date supplied by the exchange. An IP allowlist can prevent this expiry on exchanges that support it.
The installer prints one current IPv4 observation to its terminal after a successful install. Use it only if you know that IP is stable; it cannot determine that for you or guarantee that exchange traffic uses the same route. The value is never stored or sent to Ionide.
Rotating or revoking a key
Revoke a key from your exchange's dashboard at any time. The bot will fail to place new trades on
that account but won't touch existing open positions. Run /secrets action:set again with a new key to
replace it, or /secrets action:remove to clear it.
Something look wrong?
If a key stops working, re-run /secrets action:test. It'll tell you if the key is invalid, expired, or
missing a required permission. Reach out on Discord if
you're stuck.