HTX Exchange Setup

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

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

---

About HTX

HTX is one of the oldest and most established cryptocurrency exchanges, founded in 2013. Key highlights:

• Rebranded from Huobi - Formerly known as Huobi Global (see important note below)
• Founded in 2013 - One of the longest-running exchanges
• Global reach - High liquidity across major trading pairs
• Standard API authentication - Uses HMAC-SHA256 signing
• HT token discounts - Holding HT tokens reduces trading fees

---

Important: HTX Name Change

⚠️ HTX was formerly known as Huobi Global

In September 2023, Huobi Global rebranded to HTX. Important details:

Aspect	Status
Exchange website	Now htx.com
API domain	Still uses api.huobi.pro
Old documentation	May reference "Huobi"
Your account	Same account, same credentials
Trading history	All preserved

If you see references to "Huobi" in API responses or older documentation, it's the same platform. The API domain (api.huobi.pro) continues to work and is the official endpoint.

---

Creating Your API Key

Follow these steps to create an API key on HTX:

Step 1: Log In to HTX

1. Go to www.htx.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 Account from the dropdown menu
3. Click API Management in the left sidebar
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 Note

1. Enter a descriptive note: 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. Verify via email if prompted
3. Click Confirm to create your key
4. Wait for the system to generate your credentials

Step 7: Copy Your Keys IMMEDIATELY

After creation, your credentials will be displayed:

• Access Key (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

HTX 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.

---

IP Binding Configuration

IP binding restricts your API key to only work from specific IP addresses. HTX calls this feature "IP Binding" (sometimes called IP whitelisting on other exchanges).

Why Use IP Binding?

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 binding. We maintain static IPs specifically for exchange API calls and will notify you before any infrastructure changes.

How to Configure IP Binding

1. In API Management, find your SignalBee API key
2. Click Edit next to the key
3. Enable Bind IP address
4. Enter each SignalBee IP address provided by support
5. Click Save
6. Complete security verification if prompted

If You Skip IP Binding

If you choose not to use IP binding:

1. Leave IP binding 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 HTX 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 HTX from the exchange list

Step 3: Enter Your Credentials

HTX uses a simple two-value API system:

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

Note: HTX requires only 2 credentials (Access 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 HTX 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.

---

HTX-Specific Considerations

Ticker Format

HTX uses lowercase ticker symbols without separators internally:

SignalBee handles this conversion automatically. Use the standard hyphen-separated format (BTC-USDT) in your webhooks - SignalBee converts to HTX's lowercase format behind the scenes.

Supported Order Types

HTX spot trading supports the following order types:

Important: HTX spot does not support pure stop-market orders. If your strategy requires stop-loss orders, they will be placed as stop-limit orders with a limit price slightly away from the stop trigger price.

Account Types

HTX offers multiple account types:

SignalBee connects to your Spot account for trading.

Minimum Order Sizes

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

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

Trading Fees

Fee Discounts:

Tip: Check HTX's fee schedule for the most current rates and discount tiers.

API Rate Limits

• HTX enforces rate limits per API endpoint
• SignalBee handles rate limiting automatically
• If you see rate limit errors, reduce your signal frequency or check for duplicate webhooks

No Testnet Available

⚠️ Important: HTX does not offer a public testnet for spot trading.

Warning: Since there's no testnet, all testing happens on your real account with real funds. Start with minimal amounts (e.g., $5-10) when first testing your SignalBee integration with HTX.

---

Troubleshooting

Common HTX-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 binding - Disable IP binding temporarily to test
4. Wait a few minutes - New API keys may take 1-2 minutes to propagate
5. Check HTX status - Verify HTX is not under maintenance

Signature Errors Are Common

HTX uses URL-based HMAC-SHA256 signing, which is sensitive to:

• Extra whitespace in the Secret Key
• Special characters not being copied correctly
• Browser autofill adding unwanted characters

If you see signature errors:

1. Delete the credentials in SignalBee
2. Go back to HTX API Management
3. Create a new API key
4. Copy the new Secret Key immediately and carefully
5. Paste directly into SignalBee without editing

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

---

Security Best Practices

Follow this checklist to keep your HTX account secure:

HTX Account Security

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

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 binding 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 HTX - delete any you don't recognize
• Rotate API keys every 90 days as a security habit
• Monitor trade history on HTX 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
• BingX Exchange Setup - Similar two-value API setup