Bitget Exchange Setup
Connect your Bitget account to SignalBee in minutes. This guide walks you through creating and configuring API keys with the exact permissions needed for automated trading.
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
- 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 Security → Google Authenticator in your Bitget account.
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?
| Credential | What It Is | Can View Later? |
|---|---|---|
| API Key | Public identifier for your key | ✅ Yes - visible in API Management |
| Secret Key | Private key for signing requests | ❌ No - shown only once |
| Passphrase | Password you create for this key | ❌ No - you set it yourself |
All three values are required for SignalBee to connect to your Bitget 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.
Creating Your API Key
Follow these steps to create an API key on Bitget.
Step 1: Log In to Bitget
- Go to www.bitget.com
- Log in with your email/phone and password
- Complete 2FA verification
Step 2: Navigate to API Management
- Click your profile icon in the top-right corner
- Select API Management from the dropdown menu
- You'll see a list of your existing API keys (if any)
Step 3: Create a New API Key
- Click the Create API button
- You may need to complete 2FA verification again
Step 4: Configure Your API Key
- API Name - Enter a descriptive label:
SignalBee Trading - 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 (see Configuring Permissions section for details):
- ✅ Enable Read - View account info
- ✅ Enable Trade - Place orders
- ❌ Do NOT enable Withdraw - Never needed
Step 6: IP Whitelist (Optional)
- Leave empty for unrestricted access, OR
- Add specific IP addresses for enhanced security (see IP Whitelist Configuration)
Step 7: Complete Security Verification
- Authenticator Code - Enter the 6-digit 2FA code
- Email Verification - Click the link sent to your email (if required)
- Wait for verification to complete
Step 8: Save ALL THREE Values IMMEDIATELY
After verification, Bitget displays your API credentials. You MUST save all three:
| Value | Can View Later? | Action Required |
|---|---|---|
| API Key | ✅ Yes | Copy and save |
| Secret Key | ❌ NO - Never shown again | Copy immediately! |
| Passphrase | ❌ NO - You created this | Already 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
| Permission | Enable? | Why |
|---|---|---|
| Read | ✅ Yes | Allows SignalBee to check your balances and account info |
| Trade | ✅ Yes | Allows SignalBee to place and manage spot orders |
Never Enable These Permissions
| Permission | Enable? | Why |
|---|---|---|
| Withdraw | ❌ NEVER | SignalBee never needs withdrawal access. Enabling this is a serious security risk. |
| Transfer | ❌ No | Not required for spot trading |
Security Note: Even if your API key is somehow compromised, funds cannot be withdrawn without withdrawal permissions enabled. This is your most important security protection.
How to Edit Permissions
- In API Management, find your SignalBee API key
- Click the Edit button next to the key
- Modify the permission checkboxes as needed
- Click Confirm
- 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?
| Scenario | Without Whitelist | With 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
- When creating or editing your API key, find the IP Addresses section
- Enter each SignalBee IP address (one per line)
- Click Confirm
- Complete verification
If You Skip IP Whitelisting
If you choose not to use IP whitelisting:
- Leave the IP address field empty
- Understand this is less secure but still safe if withdrawals are disabled
- Your other security measures (no withdrawal permission) still protect your funds
Adding to SignalBee
Now connect your Bitget API key to SignalBee.
Step 1: Go to Exchanges Page
- Log in to your SignalBee account
- Navigate to Exchanges in the main menu
Step 2: Add New Exchange
- Click the Add Exchange button
- Select Bitget from the exchange list
Step 3: Enter Your Credentials
Bitget requires three fields - this is similar to KuCoin and OKX:
- API Key - Paste your Bitget API key
- Secret Key - Paste your Bitget Secret key
- Passphrase - Enter the 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
- Click Save and Test Connection
- Wait for SignalBee to verify your credentials
- Look for the ✅ success message
Step 5: Verify Your Setup
After successful connection:
- Your Bitget balances should appear in SignalBee
- Check that your expected assets are listed
- Balances confirm the Read permission is working
Bitget-Specific Considerations
Ticker Format
Bitget uses a concatenated format for trading pair symbols (no separator):
| SignalBee Format | Bitget Format | ⚠️ Not This |
|---|---|---|
| BTC/USDT | BTCUSDT | |
| ETH/USDT | ETHUSDT | |
| SOL/USDT | SOLUSDT |
SignalBee automatically handles format conversion—when configuring webhooks, you can use standard formats like BTC-USDT and SignalBee will convert to Bitget's BTCUSDT format.
Account Types
Bitget separates funds into different accounts. Funds must be in the Spot account for spot trades:
| Account | Purpose | For SignalBee? |
|---|---|---|
| Spot | Spot trading | ✅ Use this |
| Futures | Futures/derivatives | ⚠️ Not for spot trading |
| Copy Trade | Copy trading | ⚠️ Separate feature |
| Earn | Staking/savings | ❌ Cannot trade |
Minimum Order Sizes
Bitget enforces minimum order values:
| Typical Minimum | Notes |
|---|---|
| ~$5 USD equivalent | Varies by trading pair |
| Check specific pair | Some pairs have different minimums |
Tip: Check Bitget's trading rules for current minimum order sizes for specific pairs.
Trading Fees
| Fee Type | Standard Rate |
|---|---|
| Maker | 0.10% |
| Taker | 0.10% |
Tip: Hold BGB (Bitget's native token) in your account to get fee discounts. VIP levels also reduce trading fees.
API Rate Limits
- Bitget imposes rate limits of 10 requests per second per endpoint
- SignalBee handles rate limiting automatically
- If you see rate limit errors, reduce your signal frequency or check for duplicate webhooks
Troubleshooting
Common Bitget-specific errors and solutions:
| Error | Likely Cause | Solution |
|---|---|---|
| "Invalid API Key" | Typo when copying, or key was deleted | Re-copy the API key carefully. Check for extra spaces. Verify key exists in Bitget. |
| "Invalid Signature" | Incorrect Secret Key | Re-copy the Secret Key. Make sure there are no extra spaces or characters. |
| "Invalid Passphrase" | Wrong passphrase entered | Enter the exact passphrase you created during API key setup. It's case-sensitive. If forgotten, create a new API key. |
| "Permission Denied" | Missing required permissions | Enable Read and Trade permissions in Bitget API settings. |
| "Insufficient Balance" | Not enough funds in Spot account | Check that funds are in your Spot account, not Futures or Earn. |
| "Invalid Symbol" | Wrong ticker format | Use concatenated format: BTCUSDT, not BTC-USDT or BTC/USDT. |
| "Order amount too small" | Order below minimum | Increase order quantity to meet Bitget minimums (~$5). |
| "Rate Limit Exceeded" | Too many API requests | Wait a moment and retry. Check for duplicate webhooks. |
Connection Test Fails?
If your connection test fails in SignalBee:
- Verify all THREE values - API Key, Secret Key, AND Passphrase must all be correct
- Check the Passphrase - Most common error. Must match exactly what you set.
- Wait a few minutes - New API keys may take 1-2 minutes to activate
- Verify permissions - Ensure Read permission is enabled
- Check IP whitelist - If you configured IP restrictions, ensure SignalBee's IPs are included
For persistent issues, see our Error Codes Reference or contact support@signalbee.trade.
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 - don't reuse keys across services
- Use a strong, unique Passphrase - treat it like a password
- 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.)
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 history on Bitget for any unauthorized activity
- Keep your email secure - it's used for Bitget account recovery
Security Note: Even with all these 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.
Related Resources
- API Key Best Practices - General API key security guidance
- Security Overview - How SignalBee protects your data
- Error Codes Reference - Common error messages explained
- KuCoin Setup - Similar three-value authentication system
- OKX Setup - Another exchange with passphrase requirement