Bitfinex Exchange Setup
Connect your Bitfinex account to SignalBee in minutes. This guide walks you through creating and configuring API keys with the exact permissions needed for automated trading.
Good News: Bitfinex uses a simple two-value authentication system - just API Key and API Secret. No passphrase required.
Prerequisites
Before you begin, make sure you have:
- Verified Bitfinex account - Identity verification (KYC) completed
- 2FA enabled on Bitfinex - Required for API key creation
- SignalBee account - Ready to connect an exchange
- Password manager - For storing your API credentials securely
Security Note: Bitfinex requires 2FA (two-factor authentication) to create API keys. If you haven't enabled 2FA yet, go to Account → Security → Two-Factor Authentication in your Bitfinex account.
Understanding Bitfinex Wallet Structure
Bitfinex uses three separate wallets for different purposes. Funds must be in the Exchange wallet for spot trading with SignalBee:
| Wallet | Purpose | For SignalBee? |
|---|---|---|
| Exchange | Spot trading | ✅ Funds needed here |
| Margin | Margin trading | ❌ Not for spot |
| Funding | P2P lending | ❌ Not for trading |
How to Transfer Funds to Exchange Wallet
If your funds are in the Margin or Funding wallet:
- Log in to Bitfinex
- Go to Wallets in the main navigation
- Find the asset you want to move
- Click the Transfer icon next to the asset
- Select source wallet → Exchange wallet
- Enter the amount and confirm
Tip: Internal wallet transfers on Bitfinex are free and instant.
Creating Your API Key
Follow these steps to create an API key on Bitfinex.
Step 1: Log In to Bitfinex
- Go to www.bitfinex.com
- Log in with your email and password
- Complete 2FA verification
Step 2: Navigate to API Key Management
- Click your profile icon in the top-right corner
- Select Account from the dropdown menu
- Click API 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 New Key button
- You'll see a permissions configuration screen
Step 4: Configure Permissions
Configure the permissions for your API key (see Configuring Permissions for details):
- ✅ Enable Account History (Read) - View trade history
- ✅ Enable Orders (Read/Write) - Place and manage orders
- ✅ Enable Wallets (Read) - View balances
- ❌ Do NOT enable Withdraw - Never needed
Step 5: Label Your API Key
- Enter a descriptive label:
SignalBee Trading - This helps you identify this key's purpose later
Tip: Use a clear label like "SignalBee-Spot" so you can easily distinguish it from other API keys.
Step 6: Complete Security Verification
- Complete 2FA verification (authenticator app code)
- Confirm via email if required
- Wait for verification to complete
Step 7: Copy BOTH Values IMMEDIATELY
After verification, Bitfinex displays your API credentials:
| Value | Can View Later? | Action Required |
|---|---|---|
| API Key | ✅ Yes | Copy and save |
| API Secret | ❌ NO - Never shown again | Copy immediately! |
Warning: If you close this page without copying your API Secret, you'll need to delete this API key and create a new one. There is no way to recover an API Secret.
Save both values in your password manager now before proceeding.
Configuring Permissions
Configure the correct permissions to balance functionality and security.
Required Permissions
| Permission | Enable? | Why |
|---|---|---|
| Account History (Read) | ✅ Yes | Allows SignalBee to view your trade history |
| Orders (Read/Write) | ✅ Yes | Allows SignalBee to place and cancel spot orders |
| Wallets (Read) | ✅ Yes | Allows SignalBee to check your balances |
Never Enable These Permissions
| Permission | Enable? | Why |
|---|---|---|
| Withdraw | ❌ NEVER | SignalBee never needs withdrawal access. Enabling this is a serious security risk. |
| Funding | ❌ No | Not needed 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
If you need to modify permissions after creating your key:
- In API Management, find your SignalBee API key
- Click on the key to expand its settings
- Modify the permission checkboxes as needed
- Click Save
- 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
- In your API key settings, find the IP address section
- Enter each SignalBee IP address (one per line or comma-separated)
- Click Save
- Complete verification
If You Skip IP Whitelisting
If you choose not to use IP whitelisting:
- Leave the IP whitelist 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 Bitfinex 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 Bitfinex from the exchange list
Step 3: Enter Your Credentials
Bitfinex requires only two fields - simpler than some other exchanges:
- API Key - Paste your Bitfinex API key
- API Secret - Paste your Bitfinex API Secret
Note: No passphrase is required. Bitfinex uses a straightforward two-value authentication system (similar to Binance).
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 Bitfinex balances should appear in SignalBee
- Check that your expected assets are listed
- Balances confirm the Wallets permission is working
Tip: If balances don't appear, verify that funds are in your Exchange wallet (not Margin or Funding). See Understanding Bitfinex Wallet Structure above.
Bitfinex-Specific Considerations
Ticker Format
Bitfinex uses a unique 't' prefix in trading pair symbols:
| SignalBee Format | Bitfinex Format | ⚠️ Not This |
|---|---|---|
| BTC/USD | tBTCUSD | |
| ETH/USD | tETHUSD | |
| BTC/USDT | tBTCUST |
Note: SignalBee automatically handles ticker format conversion. You can use standard formats, and SignalBee will normalize them to Bitfinex's 't' prefix format.
Authentication Method
Bitfinex uses HMAC-SHA384 for API authentication - different from most exchanges that use HMAC-SHA256. SignalBee handles this automatically - no configuration needed on your part.
Minimum Order Sizes
Bitfinex enforces higher minimum order values than many other exchanges:
| Typical Minimum | Notes |
|---|---|
| ~$25 USD equivalent | Higher than most exchanges |
| Check specific pair | Minimums vary by trading pair |
Warning: Orders below the minimum will be rejected. Ensure your order size meets Bitfinex's minimums to avoid errors.
Trading Fees
Bitfinex has slightly higher taker fees than some competitors:
| Fee Type | Standard Rate | Notes |
|---|---|---|
| Maker | 0.10% | Competitive rate |
| Taker | 0.20% | Higher than some exchanges |
Tip: Volume discounts and LEO token holdings can reduce your fees. Check Bitfinex's fee schedule for details.
API Rate Limits
- Bitfinex imposes per-endpoint 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
Troubleshooting
Common Bitfinex-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 Bitfinex. |
| "Invalid Signature" | Incorrect API Secret | Re-copy the API Secret exactly. If lost, delete the API key and create a new one. |
| "Permission Denied" | Missing required permissions | Enable Account History, Orders, and Wallets permissions in Bitfinex API settings. |
| "IP not whitelisted" | API key restricted to different IPs | Add SignalBee's IPs to your whitelist, or remove IP restrictions. |
| "Insufficient Balance" | Funds not in Exchange wallet | Transfer funds to your Exchange wallet (not Margin or Funding). |
| "Invalid Symbol" | Wrong ticker format | Bitfinex uses tBTCUSD format. SignalBee normalizes automatically. |
| "Order amount too small" | Order below ~$25 minimum | Increase order size to meet Bitfinex's higher minimum requirements. |
| "Rate Limit Exceeded" | Too many API requests | Wait and retry. Reduce signal frequency 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 Wallets (Read) permission is enabled
- Check IP whitelist - Remove IP restrictions temporarily to test
- Verify API Secret - Remember, it's only shown once during creation
For persistent issues, see our Error Codes Reference or contact support@signalbee.trade.
Security Best Practices
Follow this checklist to keep your Bitfinex account secure:
Bitfinex Account Security
- Enable 2FA with an authenticator app (Google Authenticator, Authy) - more secure than SMS
- Use a unique, strong password for Bitfinex (not reused from other sites)
- Enable withdrawal whitelist on Bitfinex - restricts withdrawals to pre-approved addresses only
- Verify you're on the real Bitfinex site (check the URL carefully)
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 API Secret via email, chat, or screenshots
- Store both credentials in a password manager (1Password, Bitwarden, etc.)
Ongoing Security
- Review your API keys periodically in Bitfinex - delete any you don't recognize
- Rotate API keys every 90 days as a security habit
- Monitor trade history on Bitfinex for any unauthorized activity
- Keep your email secure - it's used for Bitfinex 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 Setup - Similar two-value authentication system