Bitrue Exchange Setup
Connect your Bitrue 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 Bitrue account - Identity verification (KYC) completed
- 2FA enabled on Bitrue - Required for API key creation
- SignalBee account - Ready to connect an exchange
- Password manager - For storing your API credentials securely
Security Note: Bitrue requires 2FA (two-factor authentication) to create API keys. If you haven't enabled 2FA yet, go to Security Settings → Google Authentication in your Bitrue account settings.
Creating Your API Key
Follow these steps to create an API key on Bitrue:
Step 1: Log In to Bitrue
- Go to www.bitrue.com
- Log in with your email and password
- Complete 2FA verification if prompted
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
- Enter a descriptive label:
SignalBee Trading - 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 4: Configure Permissions
- Check the permission boxes as described in the Configuring Permissions section below
- Ensure only Read and Trade are enabled
- Leave Withdraw unchecked
Step 5: Complete Security Verification
Bitrue requires verification steps to confirm API creation:
- Google Authenticator - Enter the 6-digit code from your authenticator app
- Email Verification - Enter the verification code sent to your registered email
- Wait for verification to complete
Step 6: Copy Your Keys IMMEDIATELY
After verification, Bitrue displays your API credentials:
- API Key - Can be viewed later in your API Management page
- Secret Key - ⚠️ Shown only ONCE - Copy it immediately!
| Key | Can View Later? | Action Required |
|---|---|---|
| API Key | ✅ Yes | Copy and save |
| Secret Key | ❌ NO - Never shown again | Copy 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
API permissions control what actions SignalBee can perform on your account. This is critical for 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. |
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
If you need to modify permissions on an existing key:
- In API Management, find your SignalBee API key
- Click Edit next to the key
- Check/uncheck the permission boxes as shown above
- Click Save
- 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?
| 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
- In API Management, find your SignalBee API key
- Click Edit or access the IP restriction settings
- Enable IP Restriction or Trusted IP option
- Enter each SignalBee IP address provided by support
- Click Save
- Complete 2FA verification if prompted
If You Skip IP Whitelisting
If you choose not to use IP whitelisting:
- Leave IP restrictions disabled
- 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 Bitrue 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 Bitrue from the exchange list
Step 3: Enter Your Credentials
Bitrue uses a simple two-value API system:
- API Key - Paste your Bitrue API key
- Secret Key - Paste your Bitrue Secret key
- Label (optional) - Enter a name like "Bitrue Main Account"
Note: Bitrue requires only 2 credentials (API Key + Secret Key). This is simpler than some other exchanges that require additional fields like a passphrase.
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 Bitrue balances should appear in SignalBee
- Check that your expected assets are listed
- Balances confirm the Read permission is working
Tip: If balances don't appear, verify that Read permission is enabled in your Bitrue API settings.
Bitrue-Specific Considerations
Ticker Format
Bitrue uses concatenated ticker symbols without separators (same format as Binance):
| SignalBee Format | Bitrue Format |
|---|---|
| BTC/USDT | BTCUSDT |
| ETH/USDT | ETHUSDT |
| XRP/USDT | XRPUSDT |
SignalBee handles this conversion automatically. When configuring your webhooks or whitelists, you can use either format.
Supported Order Types
Bitrue spot trading supports the following order types:
| Order Type | Supported | Notes |
|---|---|---|
| Market Order | ✅ Yes | Executes immediately at best available price |
| Limit Order | ✅ Yes | Executes at specified price or better |
| Stop Order | ❌ No | Not available on Bitrue spot trading |
Note: If your trading strategy requires stop-loss or take-profit orders as separate order types, these must be managed at the strategy level rather than as native exchange orders.
Minimum Order Sizes
Bitrue enforces minimum order values. Orders below these minimums will be rejected:
| Trading Pair | Minimum Notional Value |
|---|---|
| Most USDT pairs | Varies by pair |
| Most BTC pairs | Varies by pair |
Tip: Check Bitrue's trading rules for current minimum order sizes for specific pairs.
Trading Fees
| Fee Type | Standard Rate |
|---|---|
| Maker | Check Bitrue for current rates |
| Taker | Check Bitrue for current rates |
Tip: Bitrue offers competitive trading fees. Check their fee schedule for the most current rates and any VIP tier discounts based on trading volume.
API Rate Limits
- Bitrue 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
No Testnet Available
Unlike some exchanges, Bitrue does not offer a testnet or sandbox environment. All API testing occurs on the live production environment.
Tip: Start with small order sizes when first testing your SignalBee integration with Bitrue.
Binance Compatibility
Bitrue uses a Binance-compatible API, which means:
- Similar authentication method (HMAC-SHA256 signatures)
- Familiar error codes and response formats
- Consistent ticker format
- If you're familiar with Binance, Bitrue will feel similar
Troubleshooting
Common Bitrue-specific errors and solutions:
| Error | Code | Likely Cause | Solution |
|---|---|---|---|
| Rate Limit Exceeded | -1003 | Too many API requests | Wait a few seconds and retry. Reduce signal frequency if persistent. |
| Invalid Timestamp | -1021 | Clock synchronization issue | Usually temporary. SignalBee handles time sync automatically. Wait and retry. |
| Invalid Signature | -1022 | Incorrect Secret Key | Re-copy the Secret Key carefully. If lost, delete the API key and create a new one. |
| Invalid API Key Format | -2014 | Malformed API key | Re-copy the API key. Check for extra spaces or missing characters. |
| Invalid API Key | -2015 | Key deleted or typo | Verify key exists in Bitrue API Management. Re-copy if needed. |
| Insufficient Balance | -2010 | Not enough funds | Transfer funds to your spot wallet or reduce order size. |
| Order Not Found | -2013 | Invalid order ID | Order may have been filled or cancelled. Check order history. |
| Filter Failure | -1013 | Below minimum or price filter | Increase order quantity or adjust price to meet exchange requirements. |
| HTTP 429 | - | Rate limited | Wait and retry. Reduce request frequency. |
| HTTP 418 | - | IP banned temporarily | Wait or contact Bitrue support if persistent. |
Connection Test Fails?
If your connection test fails in SignalBee:
- Double-check both keys - Copy-paste errors are the most common issue
- Wait a few minutes - New API keys may take 1-2 minutes to activate
- Verify permissions - Ensure Read permission is enabled
- Check IP whitelist - Disable IP restriction temporarily to test
- Check Bitrue status - Verify Bitrue 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 Bitrue account secure:
Bitrue Account Security
- Enable 2FA with Google Authenticator - more secure than SMS
- Use a unique, strong password for Bitrue (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 Bitrue - delete any you don't recognize
- Rotate API keys every 90 days as a security habit
- Monitor trade history on Bitrue for any unauthorized activity
- Keep your email secure - it's used for Bitrue 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
- Binance Exchange Setup - Similar setup process (Binance-compatible API)