BingX Exchange Setup
Connect your BingX 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 BingX account - Identity verification (KYC) completed
- 2FA enabled on BingX - Required for API key creation
- SignalBee account - Ready to connect an exchange
- Password manager - For storing your API credentials securely
Security Note: BingX requires 2FA (two-factor authentication) to create API keys. If you haven't enabled 2FA yet, go to User Center → Security in your BingX account.
About BingX
BingX is a global cryptocurrency exchange known for its copy trading features and competitive fees. Key highlights:
- Copy trading focus - Popular platform for social and copy trading
- Competitive fees - 0.1% maker/taker fees on spot
- Global reach - Available in 100+ countries
- Strong API documentation - Well-documented REST API
Creating Your API Key
Follow these steps to create an API key on BingX:
Step 1: Log In to BingX
- Go to www.bingx.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 User Center from the dropdown menu
- Click API Management in the left sidebar
- 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'll be presented with the API configuration screen
Step 4: Enter a Description
- 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 5: Configure Permissions
- Check the permission boxes as described in the Configuring Permissions section below
- Enable Read and Spot Trade permissions
- Never enable the Withdrawal permission
Step 6: Complete Security Verification
- Enter your 2FA code from your authenticator app
- Click Confirm to create your key
- 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!
| Key | Can View Later? | Action Required |
|---|---|---|
| API Key | ✅ Yes | Copy and save |
| Secret Key | ❌ NO - Never shown again | Copy 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
BingX has a straightforward permission system. This is critical for security.
Required Permissions
| Permission | Enable? | Why |
|---|---|---|
| Read | ✅ Yes | Allows SignalBee to check your balances and account info |
| Spot 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. |
| Futures Trade | ❌ No | Not needed for spot trading with SignalBee |
| Transfer | ❌ No | Not needed for SignalBee trading |
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.
Simpler Than Some Exchanges
BingX uses a simple permission model:
| Exchange | Trading Permission Model |
|---|---|
| BingX | Two permissions: Read + Spot Trade |
| Bitstamp | Six separate permissions (buy/sell × limit/market/open) |
| OKX | Three credentials + multiple permissions |
This makes BingX 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?
| 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 next to the key
- Enable IP Address Restriction
- 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 BingX 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 BingX from the exchange list
Step 3: Enter Your Credentials
BingX uses a simple two-value API system:
- API Key - Paste your BingX API key
- Secret Key - Paste your BingX Secret key
- Label (optional) - Enter a name like "BingX Main Account"
Note: BingX 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
- 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 BingX 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 on your API key.
BingX-Specific Considerations
Ticker Format
BingX uses hyphen-separated ticker symbols, which matches SignalBee's native format:
| SignalBee Format | BingX Format |
|---|---|
| BTC-USDT | BTC-USDT |
| ETH-USDT | ETH-USDT |
| XRP-USDT | XRP-USDT |
| SOL-USDT | SOL-USDT |
No conversion needed! Your webhook symbols work directly with BingX.
Supported Order Types
BingX 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 via spot API |
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.
Account Types
BingX offers multiple account types:
| Account | Purpose |
|---|---|
| Standard | Spot trading (use this with SignalBee) |
| Perpetual | Futures/derivatives trading |
| Copy Trade | Social/copy trading features |
SignalBee connects to your Standard (spot) account for trading.
Minimum Order Sizes
BingX enforces minimum order values. Orders below these minimums will be rejected:
| Trading Pair | Minimum Notional Value |
|---|---|
| Most USDT pairs | ~$5 USDT |
| Varies by pair | Check BingX for specifics |
Tip: Check BingX's trading rules for current minimum order sizes for specific pairs.
Trading Fees
| Fee Type | Rate |
|---|---|
| Maker | 0.1% |
| Taker | 0.1% |
Tip: Check BingX's fee schedule for the most current rates and any VIP tier discounts.
API Rate Limits
- BingX provides rate limit information via response headers
- Headers include
X-RateLimit-Limit,X-RateLimit-Remaining, andX-RateLimit-Reset - SignalBee handles rate limiting automatically
- If you see rate limit errors, reduce your signal frequency or check for duplicate webhooks
No Testnet Available
⚠️ Important: Unlike some exchanges, BingX does not offer a public testnet for spot trading.
| Testing Approach | Recommendation |
|---|---|
| Production testing | Start with very small order sizes |
| Paper trading | Use SignalBee's simulation mode if available |
| Signal verification | Test webhook delivery before enabling live trading |
Tip: Start with small order sizes (e.g., $10-20) when first testing your SignalBee integration with BingX.
Troubleshooting
Common BingX-specific errors and solutions:
| Error | Code | Likely Cause | Solution |
|---|---|---|---|
| Invalid Signature | 100001 | Incorrect Secret Key | Re-copy the Secret Key carefully. If lost, create new key. |
| Invalid API Key | 100002 | Wrong key or deleted | Re-copy API key. Verify key exists in API Management. |
| IP Not Whitelisted | 100003 | IP restriction blocking request | Add SignalBee IPs or disable IP restriction. |
| Permission Denied | 100004 | Missing required permission | Enable Read and Spot Trade permissions. |
| Timestamp Error | 100005 | Clock synchronization issue | SignalBee handles time sync automatically. Wait and retry. |
| Request Timeout | 100006 | Slow network response | Check network. Wait and retry. |
| Rate Limit Exceeded | 100008 | Too many API requests | Wait and retry. Reduce request frequency. |
| Insufficient Balance | 80014 | Not enough funds | Deposit funds or reduce order size. |
| Order Not Found | 100412 | Invalid order ID | Order may have been filled or cancelled. |
| Invalid Symbol | 100416 | Wrong trading pair format | Use hyphen format: BTC-USDT, not BTCUSDT. |
| Min Notional Error | 100421 | Order value too small | Increase order size above minimum. |
| Too Many Requests | 100429 | Rate limit hit | Wait and retry. Consider reducing signal frequency. |
| System Busy | 100501 | Server overload | Wait a few seconds and retry. |
| Under Maintenance | 100503 | Scheduled maintenance | Wait for maintenance to complete. |
Connection Test Fails?
If your connection test fails in SignalBee:
- Double-check both keys - Copy-paste errors are the most common issue
- Verify permissions - Ensure Read and Spot Trade permissions are enabled
- Check IP whitelist - Disable IP restriction temporarily to test
- Wait a few minutes - New API keys may take 1-2 minutes to propagate
- Check BingX status - Verify BingX 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 BingX account secure:
BingX Account Security
- Enable 2FA with Google Authenticator - more secure than SMS
- Use a unique, strong password for BingX (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 BingX - delete any you don't recognize
- Rotate API keys every 90 days as a security habit
- Monitor trade history on BingX 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