SignalBee
Docs/Perpetual Exchange Guides

Bitget Perpetual Futures Setup

Connect your Bitget Futures account to SignalBee for automated perpetual contract trading. This guide walks you through enabling futures trading, creating API keys with the correct permissions, and configuring your account for automated signals.

Important: Bitget requires three values for API authentication: API Key, Secret Key, AND Passphrase. You create the Passphrase yourself during API key setup—save all three immediately.


Prerequisites

Before you begin, make sure you have:

  • Verified Bitget account - Identity verification (KYC) completed
  • 2FA enabled on Bitget - Required for API key creation
  • Futures trading enabled - Must activate Futures on your Bitget account
  • SignalBee account - Ready to connect an exchange
  • Password manager - For storing your THREE API credentials securely

Security Note: Bitget requires 2FA (two-factor authentication) to create API keys. If you haven't enabled 2FA yet, go to SecurityGoogle Authenticator in your Bitget account.


About Bitget Futures

Bitget is a major cryptocurrency derivatives exchange offering USDT-margined perpetual contracts:

FeatureDetails
Contract TypeUSDT-margined perpetual contracts
LeverageUp to 125x (varies by symbol)
Order TypesMarket, Limit, Stop-Loss, Take-Profit
Position ModesOne-way or Hedge (long + short simultaneously)
Margin TypesCross (shared) or Isolated (per position)
Funding RateEvery 8 hours
TestnetAvailable at api-simulated.bitget.com

Order Type Support

SignalBee supports most Bitget Futures order types:

Order TypeSupportedBitget API TypeDescription
Market✅ YesmarketImmediate execution at current price
Limit✅ YeslimitExecute at specified price or better
Stop-Loss✅ Yesmarket + triggerMarket order when mark price reaches trigger
Stop-Loss Limit✅ Yeslimit + triggerLimit order when trigger price is reached
Take-Profit✅ Yesmarket + triggerMarket order when take-profit price is reached
Take-Profit Limit✅ Yeslimit + triggerLimit order when take-profit price is reached
Trailing Stop❌ NoNot supported on Bitget Perpetual

Note: Unlike Binance Futures, trailing stop orders are NOT supported on Bitget Perpetual. If your strategy requires trailing stops, consider an alternative exchange or use manual stop adjustments.

Time in Force Options

OptionAPI ValueDescription
Good Till CanceledgtcOrder remains until filled or canceled (default)
Immediate or CanceliocFill immediately or cancel unfilled portion
Fill or KillfokFill entire order immediately or cancel completely
Post Onlypost_onlyOnly maker orders (adds liquidity, no taker fees)

Understanding Bitget's Passphrase System

Bitget uses a three-value authentication system for API access, similar to KuCoin and OKX.

What Are the Three Credentials?

CredentialWhat It IsCan View Later?
API KeyPublic identifier for your key✅ Yes - visible in API Management
Secret KeyPrivate key for signing requestsNo - shown only once
PassphrasePassword you create for this keyNo - you set it yourself

All three values are required for SignalBee to connect to your Bitget Futures account.

Why a Passphrase?

The Passphrase adds an extra layer of security. Even if someone obtains your API Key and Secret Key, they still need your Passphrase to make API requests. Think of it as a password specifically for this API key.

Warning: If you forget your Passphrase or lose your Secret Key, you must delete the API key and create a new one. There is no way to recover these values.


Enabling Futures Trading on Bitget

You must complete this section BEFORE creating your API key. If you create an API key without enabling Futures first, the key will not have Futures capabilities.

Activate Your Futures Account

  1. Go to www.bitget.com
  2. Log in with your email/phone and password
  3. Complete 2FA verification
  4. Hover over Derivatives in the main navigation menu
  5. Select USDT-M Futures from the dropdown
  6. If prompted, click to activate your Futures account
  7. Read and accept the Futures trading agreement

Transfer Funds to Futures Wallet

Funds must be in your Futures wallet, not your Spot wallet:

  1. Click Assets in the top menu
  2. Select Transfer
  3. Choose Spot as the source
  4. Choose USDT-M Futures as the destination
  5. Enter the amount of USDT to transfer
  6. Click Confirm

Important: Your Spot wallet balance does NOT affect Futures trading. You must explicitly transfer funds to trade futures.


Creating Your API Key

Follow these steps to create an API key with Futures permissions.

Step 1: Log In to Bitget

  1. Go to www.bitget.com
  2. Log in with your email/phone and password
  3. Complete 2FA verification (authenticator app)

Step 2: Navigate to API Management

  1. Click your profile icon in the top-right corner
  2. Select API Management from the dropdown menu
  3. You'll see a list of your existing API keys (if any)

Step 3: Create a New API Key

  1. Click the Create API button
  2. You may need to complete 2FA verification again

Step 4: Configure Your API Key

  1. API Name - Enter a descriptive label: SignalBee Futures
  2. Passphrase - Create a strong passphrase (8-32 characters)

Tip: Use a unique passphrase that you haven't used elsewhere. Treat it like a password—store it in your password manager immediately.

Step 5: Set Permissions

Configure the permissions for your API key:

  1. ✅ Enable Read - View account info and positions
  2. ✅ Enable Futures Trade - Place futures orders
  3. ❌ Do NOT enable Withdraw - Never needed
  4. ❌ Do NOT enable Transfer - Not required

Critical: You must enable Futures Trade permission, NOT Spot Trade. These are separate permissions.

Step 6: IP Whitelist (Optional)

  1. Leave empty for unrestricted access, OR
  2. Add specific IP addresses for enhanced security (see IP Whitelist Configuration)

Step 7: Complete Security Verification

  1. Authenticator Code - Enter the 6-digit 2FA code
  2. Email Verification - Click the link sent to your email (if required)
  3. Wait for verification to complete

Step 8: Save ALL THREE Values IMMEDIATELY

After verification, Bitget displays your API credentials. You MUST save all three:

ValueCan View Later?Action Required
API Key✅ YesCopy and save
Secret KeyNO - Never shown againCopy immediately!
PassphraseNO - You created thisAlready saved it, right?

Warning: The Secret Key is displayed only once. If you close the page without copying it, you'll need to delete this API key and create a new one.

Save all three values in your password manager now before proceeding.


Configuring Permissions

Configure the correct permissions to balance functionality and security.

Required Permissions

PermissionEnable?Why
Read✅ YesAllows SignalBee to check your balances and positions
Futures TradeYes - REQUIREDAllows SignalBee to place and manage futures orders

Never Enable These Permissions

PermissionEnable?Why
WithdrawNEVERSignalBee never needs withdrawal access. Enabling this is a serious security risk.
Transfer❌ NoNot required for SignalBee functionality
Spot TradeOptionalOnly if also using SignalBee for spot trading

Critical: You MUST enable the Futures Trade permission. Without this, SignalBee cannot place futures orders even if your API key is valid. The Spot Trade permission is separate and won't work for futures.

How to Edit Permissions

  1. In API Management, find your SignalBee Futures API key
  2. Click the Edit button next to the key
  3. Modify the permission checkboxes as needed
  4. Click Confirm
  5. Complete 2FA verification

IP Whitelist Configuration

IP whitelisting restricts your API key to only work from specific IP addresses. This is optional but adds a strong security layer.

Why Use IP Whitelisting?

ScenarioWithout WhitelistWith Whitelist
SignalBee places trade✅ Works✅ Works
Attacker tries stolen key⚠️ Could work❌ Blocked

Even if your API key is somehow exposed, it won't work from unauthorized IP addresses.

SignalBee Server IP Addresses

Note: Contact support@signalbee.trade to request SignalBee's current production IP addresses for whitelisting. We maintain static IPs specifically for exchange API calls and will notify you before any infrastructure changes.

How to Configure IP Whitelisting

  1. When creating or editing your API key, find the IP Addresses section
  2. Enter each SignalBee IP address (one per line)
  3. Click Confirm
  4. Complete verification

If You Skip IP Whitelisting

If you choose not to use IP whitelisting:

  1. Leave the IP address field empty
  2. Understand this is less secure but still safe if withdrawals are disabled
  3. Your other security measures (no withdrawal permission) still protect your funds

Adding to SignalBee

Now connect your Bitget Futures API key to SignalBee.

Step 1: Go to Exchanges Page

  1. Log in to your SignalBee account
  2. Navigate to Exchanges in the main menu

Step 2: Add New Exchange

  1. Click the Add Exchange button
  2. Select Bitget Perpetual from the exchange list

Critical: Make sure you select Bitget Perpetual, NOT "Bitget". These are different exchange connections for different account types. Selecting the wrong one will cause connection failures.

Step 3: Enter Your Credentials

Bitget Perpetual requires three fields:

FieldValue
API KeyYour Bitget API key
Secret KeyYour Bitget Secret key
PassphraseThe passphrase you created when making the API key

Tip: The Passphrase is the one YOU created during API key setup. Make sure you're entering it exactly as you set it—it's case-sensitive.

Step 4: Test the Connection

  1. Click Save and Test Connection
  2. Wait for SignalBee to verify your credentials
  3. Look for the success message

Step 5: Verify Your Setup

After successful connection:

  1. Your Bitget Futures balances should appear in SignalBee
  2. Check that your USDT balance matches your Futures wallet
  3. If you see your Spot balance instead, you may have selected the wrong exchange type

Tip: If balances don't appear or show $0, verify that:

  • You selected "Bitget Perpetual" (not "Bitget")
  • Your API key has the Futures Trade permission enabled
  • You have transferred funds to your Futures wallet

Bitget Futures-Specific Considerations

Ticker Format

Bitget Futures uses a unique format with a product type suffix:

SignalBee FormatBitget Format
BTC-USDTBTCUSDT_UMCBL
ETH-USDTETHUSDT_UMCBL
SOL-USDTSOLUSDT_UMCBL

The _UMCBL suffix identifies USDT-margined perpetual contracts. SignalBee automatically converts between formats—when configuring webhooks, use standard formats like BTC-USDT and SignalBee will handle the conversion.

Contract Types

TypeProduct TypeSymbol SuffixSignalBee Support
USDT-MUSDT-FUTURES_UMCBL✅ Primary support
USDC-M_DMCBL❌ Not implemented

SignalBee supports USDT-margined perpetual contracts only.

Minimum Order Sizes

Bitget Futures enforces minimum order values:

CategoryTypical Minimum
Major pairs (BTC, ETH)~$5 USD equivalent
Altcoin pairs~$5-10 USD equivalent

Tip: Check Bitget's trading rules for current minimums.

Trading Fees

Fee TypeStandard RateWith BGB Discount
Maker0.02%0.018% (10% off)
Taker0.06%0.054% (10% off)

Tip: Hold BGB (Bitget's native token) in your account and enable "Use BGB for fees" to get fee discounts.

API Rate Limits

  • Public endpoints: 20 requests per 2 seconds
  • Private endpoints: 10 requests per 2 seconds
  • SignalBee handles rate limiting automatically
  • If you see rate limit errors, reduce your signal frequency

Testnet for Practice

Bitget provides a simulated trading environment for practice:

  • Testnet URL: api-simulated.bitget.com
  • Create separate testnet API keys
  • Practice trading without risking real funds
  • Test your signal configurations before going live

Position Mode Configuration

Bitget Futures supports two position modes. Choose based on your trading strategy.

One-way Mode (Default)

AspectDescription
API Valueone_way_mode
BehaviorSingle position per symbol
Long + ShortNot simultaneous (close long to open short)
Best ForSimple directional trading

Hedge Mode

AspectDescription
API Valuehedge_mode
BehaviorSeparate long and short positions
Long + ShortCan hold both simultaneously
Best ForAdvanced strategies, hedging

How to Change Position Mode

  1. Go to Bitget Futures trading page
  2. Click the Settings icon (gear)
  3. Select Position Mode
  4. Choose One-way Mode or Hedge Mode
  5. Confirm the change

Important: You cannot change position mode while you have open positions or pending orders. Close all positions and cancel all orders first.


Leverage and Margin Configuration

Setting Leverage

Leverage is configured per trading pair on Bitget:

  1. Open the trading page for your desired pair (e.g., BTCUSDT)
  2. Click the leverage display (e.g., "20x")
  3. Use the slider to select your desired leverage (1x to 125x)
  4. Click Confirm
Symbol CategoryTypical Max Leverage
BTC, ETHUp to 125x
Major AltcoinsUp to 75x
Smaller AltcoinsUp to 50x

Recommendation: Start with 5x leverage or less until you're comfortable with futures trading. Higher leverage means faster liquidation.

Margin Types

TypeAPI ValueDescriptionBest For
IsolatedisolatedOnly allocated margin at risk (default)Limiting losses per trade
CrosscrossedEntire Futures wallet as marginAvoiding liquidation, larger accounts

How to Switch Margin Type

  1. On the trading page, find the margin mode indicator
  2. Click to switch between Cross and Isolated
  3. For Isolated, you can set the margin amount per position

Tip: Isolated margin limits your maximum loss to the margin allocated to that position. Cross margin uses your entire Futures balance.

Understanding Liquidation

When your position losses exceed your margin:

  • Your position is automatically closed (liquidated)
  • You lose the margin allocated to that position
  • With cross margin, liquidation uses more of your wallet balance

Liquidation price is shown on each open position. Always know your liquidation price before entering a trade.


Troubleshooting

Common Bitget Futures-specific errors and solutions:

ErrorCodeLikely CauseSolution
Invalid API Key30001-30003Typo or deleted keyRe-copy API key carefully. Check key exists in Bitget.
Invalid Signature30004-30005Wrong Secret Key OR PassphraseVerify both Secret Key AND Passphrase. Both must match exactly.
Invalid PassphrasePassphrase doesn't matchCase-sensitive. Must match exactly what you created. If forgotten, create new API key.
Timestamp Error40004-40005, 40008Clock sync issueUsually temporary. SignalBee handles automatic retry and time sync.
Futures Permission DeniedAPI missing Futures permissionEnable Futures Trade permission (not Spot Trade) in Bitget API settings.
Insufficient Margin34001-34003Not enough funds in Futures walletTransfer funds from Spot to Futures wallet.
Leverage Setting Failed40001-40006Invalid leverage for symbolCheck maximum leverage allowed for this symbol.
Position Mode Change FailedOpen positions existClose all positions and cancel all orders first.
Quantity Too Small43008Order quantity below minimumIncrease order quantity to meet Bitget minimums.
Min Notional Error43013Order value too smallIncrease order size (quantity × price) to meet minimum.
Invalid SymbolWrong symbol formatSignalBee handles format conversion. Verify pair exists on Bitget Futures.
Order Not Found43001-43015Order already filled or canceledOrder may have been processed already.
Rate Limit50001-50002Too many requestsReduce signal frequency. SignalBee handles retries automatically.

Connection Test Fails?

If your connection test fails in SignalBee:

  1. Verify exchange selection - Must be "Bitget Perpetual", not "Bitget"
  2. Check all THREE values - API Key, Secret Key, AND Passphrase must all be correct
  3. Check the Passphrase - Most common error. Case-sensitive, must match exactly what you set.
  4. Verify Futures permission - Must have Futures Trade enabled (not just Spot Trade)
  5. Check Futures is enabled - You must have activated Futures on Bitget
  6. Wait a few minutes - New API keys may take 1-2 minutes to activate
  7. Check IP whitelist - If configured, ensure SignalBee's IPs are included

Funds Show as $0?

If SignalBee shows $0 balance:

  1. Verify exchange type - "Bitget Perpetual" shows Futures wallet, "Bitget" shows Spot wallet
  2. Transfer funds - Funds must be in Futures wallet, not Spot
  3. Check Reading permission - API key needs Read permission enabled

For persistent issues, see our Error Codes Reference or contact support@signalbee.trade.


Risk Warnings

CRITICAL: Perpetual futures trading carries significant risk. Read this section carefully.

Leverage Amplifies Both Gains AND Losses

Leverage10% Price Move Against You
1x10% loss
5x50% loss
10x100% loss (liquidated)
20xLiquidated at 5% move

Higher leverage = faster liquidation. A 1% adverse price movement with 100x leverage results in complete loss.

Liquidation is Automatic and Final

  • When margin is depleted, your position is forcibly closed
  • You lose the entire margin allocated to that position
  • There is no way to recover from liquidation
  • Liquidation fees apply on top of losses

Funding Rates Affect Position Costs

  • Perpetual contracts have funding payments every 8 hours
  • If you're long and funding is positive, you pay shorts
  • If you're short and funding is positive, you receive payment
  • Funding can significantly affect profitability of longer-term positions

Risk Management Best Practices

  • Start with low leverage (5x or less) until experienced
  • Always use stop-losses to limit potential losses
  • Never trade with funds you can't afford to lose
  • Size positions appropriately - don't risk entire account
  • Understand your liquidation price before entering trades
  • Monitor funding rates for held positions
  • Practice on testnet first before trading real funds
  • Consider isolated margin to limit maximum loss per trade

Not Suitable For

Futures trading may not be appropriate if you:

  • Are new to cryptocurrency trading
  • Cannot afford to lose your entire investment
  • Don't understand leverage and liquidation mechanics
  • Are unable to monitor positions regularly
  • Have high risk aversion

Security Best Practices

Follow this checklist to keep your Bitget account secure:

Bitget Account Security

  • Enable 2FA with an authenticator app (Google Authenticator, Authy) - more secure than SMS
  • Use a unique, strong login password for Bitget (not reused from other sites)
  • Enable anti-phishing code on Bitget - helps identify legitimate emails

API Key Security

  • Create a dedicated API key just for SignalBee Futures - don't reuse keys
  • Use a strong, unique Passphrase - treat it like a password (8-32 characters)
  • Never enable withdrawal permission - SignalBee never needs it
  • Consider IP whitelisting for maximum security
  • Never share your Secret Key via email, chat, or screenshots
  • Never share your Passphrase - it's as sensitive as your Secret Key
  • Store ALL THREE credentials in a password manager (1Password, Bitwarden, etc.)
  • Use separate API keys for Spot and Futures if using both

Ongoing Security

  • Review your API keys periodically in Bitget - delete any you don't recognize
  • Rotate API keys every 90 days as a security habit
  • Monitor trade and position history for any unauthorized activity
  • Keep your email secure - it's used for Bitget account recovery

Security Note: Even with all precautions, the most important protection is never enabling withdrawal permissions. Without this permission, your funds cannot be moved off the exchange even if everything else is compromised.