How to Connect Bybit to ZeroLoss: API Key Setup
ZeroLoss trades Bybit USDT perpetual contracts on your own Bybit account. It connects through an API key that you create on Bybit, not through your password, and the key only needs permission to read your account and trade futures. Your money stays on Bybit 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 Bybit account with Google Authenticator (2FA) turned on. Very new accounts may not be able to create API keys for their first 48 hours.
- A computer: Bybit does not let you create API keys in its app, only on the website.
- At least 100 USDT in your Unified Trading Account. Deposits arrive in the Funding Account, so move them: Assets → Transfer, from Funding Account to Unified Trading Account.
- A ZeroLoss account. You can start with the free paper test and connect later.
Step 1: Create the API key on Bybit
- Log in on the Bybit website, click the profile icon at the top right and open API, then Create New Key.
- Choose System-generated API Keys, for your own use (not “Connect to Third-Party Applications”).
- Name the key, set Read-Write, and choose the permissions (Step 2) and IP addresses (Step 3).
- Enter your Google Authenticator code to confirm.
- Copy the API Key and the Secret.
Step 2: Choose the permissions
Set the key to Read-Write; a Read-Only key is refused by ZeroLoss with a clear message. Under the contract (derivatives) permissions, allow Orders and Positions, which together let ZeroLoss place and manage USDT perpetual trades. Leave Withdraw off, and leave the account and sub-account Transfer permissions off too.
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 Bybit.
On Bybit, a key with no IP addresses bound expires after 90 days, and it also stops working seven days after you change your Bybit password. A key bound to ZeroLoss’s IPs has neither problem.
Step 4: Connect the key in ZeroLoss
- Log in to ZeroLoss and open Connect Exchange.
- Under 1 · Pick your exchange, choose Bybit.
- Under 2 · Paste your API key, paste your API key and secret key.
- Click Verify & connect. ZeroLoss checks the key and reads your futures balance. The connection needs at least 100 USDT in your Bybit Unified Trading Account.
Check that the key is safe
Open the API management page on Bybit 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 Bybit; 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
- The bot stopped after about three months: the key had no IP binding and expired at 90 days. Create a new key bound to ZeroLoss’s IPs.
- “API key invalid” on a key you just made: check it was created on bybit.com itself, not on Testnet or in Demo Trading, and on the account that holds the USDT (a sub-account key only sees that sub-account). Bybit EU (bybit.eu) is a separate platform with separate keys.
- “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 still in the Funding Account. Transfer it to the Unified Trading Account on Bybit 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.