WhiteBIT Exchange Setup

Connect your WhiteBIT 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 WhiteBIT account - Identity verification (KYC) completed
• 2FA enabled on WhiteBIT - Required for API key creation
• SignalBee account - Ready to connect an exchange
• Password manager - For storing your API credentials securely

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

---

About WhiteBIT

WhiteBIT is a European cryptocurrency exchange known for its user-friendly interface and competitive fees. Key highlights:

• European-based - Regulated exchange with strong compliance standards
• Wide trading pair selection - Extensive list of spot trading pairs
• Competitive fees - 0.1% maker/taker fees on spot markets
• WBT token benefits - Native token offers fee discounts and other perks
• Simple API setup - Straightforward two-credential authentication

---

Creating Your API Key

Follow these steps to create an API key on WhiteBIT:

Step 1: Log In to WhiteBIT

1. Go to whitebit.com
2. Log in with your email and password
3. Complete 2FA verification if prompted

Step 2: Navigate to API Management

1. Click your profile icon in the top-right corner
2. Select Profile from the dropdown menu
3. Click API Keys in the left sidebar (under Security section)
4. You'll see a list of your existing API keys (if any)

Step 3: Create a New API Key

1. Click the Create API Key button
2. You'll be presented with the API configuration screen

Step 4: Enter a Description

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

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

Step 5: Configure Permissions

1. Check the permission boxes as described in the Configuring Permissions section below
2. Enable Read and Trade permissions
3. Never enable the Withdrawal permission

Step 6: Complete Security Verification

1. Enter your 2FA code from your authenticator app
2. Click Confirm to create your key
3. Wait for the system to generate your credentials

Step 7: Copy Your Keys IMMEDIATELY

After creation, your credentials will be displayed:

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

Warning: If you navigate away 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

WhiteBIT has a straightforward permission system. This is critical for security.

Required Permissions

Never Enable These Permissions

Security Note: Even if your API key is somehow compromised, funds cannot be withdrawn without withdrawal permission enabled. This is your most important security protection.

Simple Two-Credential Setup

WhiteBIT uses a simple credential model similar to Binance:

This makes WhiteBIT one of the simpler exchanges to configure.

---

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 Keys, find your SignalBee API key
2. Click Edit next to the key
3. Enable IP Address Restriction
4. Enter each SignalBee IP address provided by support
5. Click Save
6. Complete 2FA verification if prompted

If You Skip IP Whitelisting

If you choose not to use IP whitelisting:

1. Leave IP restrictions disabled
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 WhiteBIT 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 WhiteBIT from the exchange list

Step 3: Enter Your Credentials

WhiteBIT uses a simple two-value API system:

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

Note: WhiteBIT requires only 2 credentials (API Key + Secret Key). This is simpler than exchanges like OKX or KuCoin that require an additional passphrase.

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 WhiteBIT 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 Read permission is enabled on your API key.

---

WhiteBIT-Specific Considerations

Ticker Format

WhiteBIT uses underscore-separated uppercase ticker symbols. SignalBee converts automatically:

No action needed! Your webhook symbols work directly with WhiteBIT - SignalBee handles the conversion automatically.

Supported Order Types

WhiteBIT spot trading supports the following order types:

Important: WhiteBIT only supports Market and Limit orders for spot trading. If your trading strategy requires stop-loss or take-profit orders, these must be managed at the strategy level rather than as native exchange orders.

Unified Account Structure

WhiteBIT uses a unified account model where all your funds are available for spot trading:

What this means for you:

• No need to transfer funds between accounts
• All deposited funds are immediately available for trading
• Simpler to manage than exchanges with multiple account types

HMAC-SHA512 Authentication

WhiteBIT uses HMAC-SHA512 for request signing, which differs from the HMAC-SHA256 used by most exchanges.

What this means for you:

• SignalBee handles this automatically - no action required
• Your credentials work exactly like other exchanges
• The different algorithm is completely transparent to you

Note: You don't need to understand the technical details. Just provide your API Key and Secret Key, and SignalBee handles the rest.

Minimum Order Sizes

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

Tip: Check WhiteBIT's trading rules for current minimum order sizes for specific pairs. If you receive "Min Amount" or "Min Total" errors, increase your order size.

Trading Fees

WhiteBIT offers fee discounts for WBT (WhiteBIT Token) holders. Check WhiteBIT's fee schedule for details on VIP tiers and WBT discounts.

API Rate Limits

• WhiteBIT allows approximately 1200 requests per minute per IP
• SignalBee handles rate limiting automatically
• If you see rate limit errors, reduce your signal frequency or check for duplicate webhooks

No Testnet Available

Important: WhiteBIT does not offer a public testnet for spot trading.

Tip: Start with small order sizes (e.g., $10-20) when first testing your SignalBee integration with WhiteBIT.

---

Troubleshooting

Common WhiteBIT-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. Verify permissions - Ensure Read and Trade permissions are enabled
3. Check IP whitelist - Disable IP restriction temporarily to test
4. Wait a few minutes - New API keys may take 1-2 minutes to propagate
5. Check WhiteBIT status - Verify WhiteBIT is not under maintenance

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

---

Security Best Practices

Follow this checklist to keep your WhiteBIT account secure:

WhiteBIT Account Security

• Enable 2FA with Google Authenticator - more secure than SMS
• Use a unique, strong password for WhiteBIT (not reused from other sites)
• Enable email notifications for account activity
• Review login history regularly for unauthorized access

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 WhiteBIT - delete any you don't recognize
• Rotate API keys every 90 days as a security habit
• Monitor trade history on WhiteBIT for any unauthorized activity

Security Note: Even with all these precautions, the most important protection is never enabling withdrawal permission. 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
• Binance Exchange Setup - Similar two-value API setup
• LBank Exchange Setup - Similar two-value API setup