How to Connect ZebPay to ZeroLoss: API Key Setup
ZeroLoss trades ZebPay futures, with USDT or INR margin on your own ZebPay account. It connects through an API key that you create on ZebPay, not through your password, and the key only needs permission to read your account and trade futures. Your money stays on ZebPay 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 ZebPay account with futures access: ZebPay futures are only for KYC-verified Indian users, and new orders also need your bank verification completed.
- Futures enabled on your account, and at least 100 USDT, or the rupee equivalent, in the futures wallet. On the web: Wallet → Future tab → Transfer funds, from Fiat to Futures for INR or from Crypto to Futures for USDT. Transfers are instant.
- A ZeroLoss account. You can start with the free paper test and connect later.
Step 1: Create the API key on ZebPay
- Open ZebPay’s API portal (api.zebpay.com) and go to API Trading.
- Create a new key and give it a name, such as “ZeroLoss”.
- Choose the scopes (Step 2) and the IP allowlist (Step 3).
- Confirm with the phone and email OTPs.
- Copy the API Key and the Secret.
Step 2: Choose the permissions
ZebPay calls permissions scopes. Select both:
- fetch:details: read access to your account.
- futures:trading: placing and managing futures orders.
Do not add any withdrawal scope if one is offered.
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. ZebPay lets you add an IP allowlist to the key; paste them there.
Use production keys from ZebPay’s live portal; sandbox keys are separate and will not connect.
Step 4: Connect the key in ZeroLoss
- Log in to ZeroLoss and open Connect Exchange.
- Under 1 · Pick your exchange, choose ZebPay.
- 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. When you connect, choose USDT or INR as the margin asset; the minimum is 100 USDT, or its rupee equivalent for INR.
Check that the key is safe
Open the API management page on ZebPay 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 ZebPay; 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
- Orders are refused although the key connects: ZebPay blocks new orders until KYC and bank verification are both complete.
- “Not allowed API access from this IP”: the allowlist is missing one of ZeroLoss’s addresses. Paste the full list again.
- “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 … required in Futures wallet”: the futures wallet holds less than the minimum in the margin asset you chose. Transfer more from Fiat or Crypto to Futures on ZebPay.
Trading from India? Our guide for Indian traders compares the five Indian exchanges ZeroLoss connects to, rupee versus USDT margin, and the tax basics.
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.