How to Connect Bitget Futures to ZeroLoss: API Key Setup
ZeroLoss trades Bitget USDT-M futures on your own Bitget account. It connects through an API key that you create on Bitget, not through your password, and the key only needs permission to read your account and trade futures. Your money stays on Bitget the whole time. This guide shows how to create that key, restrict it, and connect it to ZeroLoss. It takes about five minutes.
Want to see the bot trade before connecting anything? The free 7-day paper test needs no exchange at all.
Before you start
- A Bitget account with identity verification completed and Google Authenticator (2FA) turned on.
- If your account was upgraded to Bitget’s Unified Trading Account (Bitget has been moving accounts since 15 September 2026): switch it from Basic Mode to Advanced Mode. Basic Mode does not support cross margin, which ZeroLoss uses.
- At least 100 USDT for futures. On a classic account: Assets → Transfer, from Spot to USDT-M Futures. On a Unified Trading Account no transfer is needed.
- A ZeroLoss account. You can start with the free paper test and connect later.
Step 1: Create the API key on Bitget
- Log in on the Bitget website, click the profile icon and open API (API Key Management), then Create API key.
- Choose System-generated API Key.
- Name the key and set a passphrase. Write it down: Bitget cannot change or recover it, and ZeroLoss needs it.
- Set the permissions (Step 2) and the IP addresses (Step 3).
- Confirm with the email code and your Google Authenticator code, then copy the API Key and the Secret Key.
Step 2: Choose the permissions
Choose Read-Write and tick futures trading (on a Unified Trading Account this is called Unified account trade; also allow account management so leverage and position mode can be set). Leave Withdraw off and leave Transfer off.
Step 3: Restrict the key to ZeroLoss’s IP addresses
Restricting a key to a few IP addresses means it only works from those servers, even if someone copied it. In the ZeroLoss app, open Connect Exchange; the step Add our IPs lists ZeroLoss’s server addresses with a Copy all button. Paste them into the IP restriction field on Bitget.
Bitget strongly recommends binding IP addresses, and allows up to 10 per key. Bound keys also keep withdrawals impossible from anywhere else, as Bitget only allows withdrawals from whitelisted IPs.
Step 4: Connect the key in ZeroLoss
- Log in to ZeroLoss and open Connect Exchange.
- Under 1 · Pick your exchange, choose Bitget.
- Under 2 · Paste your API key, paste your API key, secret key and passphrase. The passphrase is the one you typed when you created the key on Bitget; Bitget cannot show it again.
- Click Verify & connect. ZeroLoss checks the key and reads your futures balance. The connection needs at least 100 USDT available for USDT-M futures.
Check that the key is safe
Open the API management page on Bitget and look at the key you created. It should allow reading and futures trading, with withdrawals off. To stop ZeroLoss at any time, delete the key on Bitget; trading through it ends immediately, without any action from us. Our guide to trade-only API keys explains why this is the setting that matters.
Common problems
- Trades fail on an upgraded account: the Unified Trading Account is in Basic Mode, which has no cross margin. Switch to Advanced Mode.
- Lost passphrase: Bitget cannot show it. Delete the key and create a new one.
- “Invalid API Key or Secret”: a character was missed when copying. Copy both again; if the secret was not saved, delete the key and create a new one.
- “API key missing required permissions”: futures trading or reading is not ticked on the key. Edit the key, or create a new one with both.
- “API IP restriction issue”: the key is restricted, but not to all of ZeroLoss’s addresses. Use Copy all in the app and paste the full list again.
- “Minimum 100 USDT required in Futures wallet”: your USDT is in the Spot account of a classic Bitget account. Transfer it to USDT-M Futures and try again.
Crypto futures trading carries a high risk of loss, and automation does not remove it. Exchange screens change from time to time; if a menu looks different, the permission names above are what to look for. This page is general information, not financial advice. See our Risk & Liability Disclaimer.