Binance Exchange Setup

Connect your Binance account to SignalBee in minutes. This guide walks you through creating and configuring API keys with the exact permissions needed for automated trading.

---

Prerequisites

Before you begin, make sure you have:

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

Security Note: Binance requires 2FA (two-factor authentication) to create API keys. If you haven't enabled 2FA yet, go to Security → Two-Factor Authentication in your Binance account settings.

---

Binance API Key Types

Binance offers three types of API keys. For most users, we recommend the default option:

Our recommendation: Use System-generated keys. They're secure, easy to create, and work perfectly with SignalBee. Self-generated keys are only necessary for enterprise use cases with specific key management requirements.

---

Creating Your API Key

Follow these steps to create an API key on Binance:

Step 1: Log In to Binance

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

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. Select System-generated (recommended)
3. Click Next

Step 4: Label Your API Key

1. Enter a descriptive label: SignalBee Trading
2. A clear label helps you identify this key's purpose later
3. Click Next

Tip: Use specific labels like "SignalBee-Spot" or "SignalBee-Main" if you plan to create multiple keys for different purposes.

Step 5: Complete Security Verification

Binance requires multiple verification steps:

1. Authenticator App - Enter the 6-digit code from your authenticator
2. Email Verification - Click the link sent to your registered email
3. Wait for verification to complete

Step 6: Copy Your Keys IMMEDIATELY

After verification, Binance displays your API credentials:

• API Key - Can be viewed later in your API Management page
• Secret Key - ⚠️ Shown only ONCE - Copy it immediately!

Warning: If you close this page without copying your Secret Key, you'll need to delete this API key and create a new one. There is no way to recover a Secret Key.

Save both keys in your password manager now before proceeding.

---

Configuring Permissions

After creating your API key, configure the permissions. This is critical for security.

Required Permissions

Optional Permissions

Never Enable These Permissions

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

1. In API Management, find your SignalBee API key
2. Click Edit next to the key
3. Check/uncheck the permission boxes as shown above
4. Click Save
5. Complete 2FA verification to confirm changes

---

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?

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. In API Management, find your SignalBee API key
2. Click Edit
3. Find the Restrict access to trusted IPs only option
4. Click Add IP Address
5. Enter each SignalBee IP address provided by support
6. Click Save
7. Complete 2FA verification

If You Skip IP Whitelisting

If you choose not to use IP whitelisting:

1. Select Unrestricted for IP access
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 Binance 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 Binance from the exchange list

Step 3: Enter Your Credentials

1. API Key - Paste your Binance API key
2. Secret Key - Paste your Binance Secret key
3. Label (optional) - Enter a name like "Binance Main Account"

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 Binance balances should appear in SignalBee
2. Check that your expected assets are listed
3. Balances confirm the Read permission is working

Tip: If balances don't appear, verify that Enable Reading is checked in your Binance API settings.

---

Binance-Specific Considerations

Ticker Format

Binance uses concatenated ticker symbols without separators:

When configuring your whitelist or webhooks, use the Binance format: BTCUSDT, ETHUSDT, etc.

Minimum Order Sizes

Binance enforces minimum order values. Orders below these minimums will be rejected:

Tip: Check Binance's trading rules for current minimum order sizes for specific pairs.

Trading Fees

Tip: Hold BNB in your account and enable "Use BNB for fees" in Binance settings to automatically get the 25% fee discount.

API Rate Limits

• Binance imposes rate limits on API requests
• SignalBee handles rate limiting automatically
• If you see rate limit errors, reduce your signal frequency or check for duplicate webhooks

Spot vs Futures

This guide covers Spot trading setup. For Binance Futures (USDT-M or COIN-M perpetuals):

1. Enable Futures permission on your API key
2. Ensure funds are in your Futures wallet (not Spot wallet)
3. Trading pairs use different symbols (e.g., BTCUSDT perpetual)

---

Troubleshooting

Common Binance-specific errors and solutions:

Connection Test Fails?

If your connection test fails in SignalBee:

1. Double-check both keys - Copy-paste errors are the most common issue
2. Wait a few minutes - New API keys may take 1-2 minutes to activate
3. Verify permissions - Ensure Reading permission is enabled
4. Check IP whitelist - Disable IP restriction temporarily to test
5. Try a different browser - Clear cache or use incognito mode

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

---

Security Best Practices

Follow this checklist to keep your Binance account secure:

Binance Account Security

• Enable 2FA with an authenticator app (Google Authenticator, Authy) - more secure than SMS
• Set up your anti-phishing code in Binance settings - helps identify legitimate Binance emails
• Enable withdrawal whitelist on Binance - restricts withdrawals to pre-approved addresses only
• Use a unique, strong password for Binance (not reused from other sites)

API Key Security

• Create a dedicated API key just for SignalBee - don't reuse keys across services
• Never enable withdrawal permission - SignalBee never needs it
• Consider IP whitelisting for maximum security
• Never share your Secret Key via email, chat, or screenshots
• Store keys in a password manager (1Password, Bitwarden, etc.)

Ongoing Security

• Review your API keys periodically in Binance - delete any you don't recognize
• Rotate API keys every 90 days as a security habit
• Monitor trade history on Binance for any unauthorized activity
• Keep your email secure - it's used for Binance 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