HashKey Exchange Setup

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

Important: HashKey is a regulated Hong Kong exchange. You may need to complete enhanced verification depending on your jurisdiction. Account verification requirements are stricter than unregulated exchanges.

---

About HashKey

HashKey is a Hong Kong-based cryptocurrency exchange licensed by the Securities and Futures Commission (SFC). Key highlights:

• SFC-licensed - One of the few exchanges licensed by Hong Kong's financial regulator
• Regulatory compliance - Institutional-grade compliance and security standards
• Limited trading pairs - Carefully curated selection of major cryptocurrencies
• Testnet available - Test your integration before trading with real funds
• Institutional focus - Designed to meet institutional trading requirements

Regional Note: HashKey focuses on compliant cryptocurrency trading in Hong Kong. Some features may require Hong Kong residency or enhanced verification for full access.

---

Creating Your API Key

Follow these steps to create an API key on HashKey:

Step 1: Log In to HashKey

1. Go to hashkey.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 Settings 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 Label

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: Configure IP Whitelist (Optional)

1. If you want to restrict API access to specific IPs, enable IP whitelisting
2. See IP Whitelist Configuration for details
3. You can skip this step for initial setup

Step 7: Copy Your Keys IMMEDIATELY

After completing 2FA verification, 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

HashKey uses a straightforward permission system. Configure permissions carefully 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-Permission System

HashKey uses a clean permission model similar to other modern exchanges:

This makes HashKey one of the simpler exchanges to configure securely.

---

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. During API key creation, enable IP Address Restriction
2. Enter each SignalBee IP address provided by support
3. Click Save
4. Complete 2FA verification if prompted

If You Skip IP Whitelisting

If you choose not to use IP whitelisting:

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

Step 3: Enter Your Credentials

HashKey uses a standard two-value API system:

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

Note: HashKey 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 HashKey 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.

---

HashKey-Specific Considerations

Ticker Format

HashKey uses concatenated ticker symbols internally (no separator):

SignalBee handles this conversion automatically. Use the standard hyphen format (BTC-USDT) in your webhooks and SignalBee will convert to HashKey's format.

Supported Order Types

HashKey spot trading supports the following order types:

Important: HashKey does not support stop orders on the spot market. If your trading strategy requires stop-loss or take-profit orders, these must be managed at the strategy level. Consider using market orders to exit positions when your strategy signals an exit.

Limited Trading Pairs

HashKey offers a more limited selection of trading pairs compared to global exchanges:

• Focus on major cryptocurrencies (BTC, ETH, and select altcoins)
• Primarily USDT pairs
• Quality over quantity - curated for compliance

Tip: Check HashKey's trading page for the current list of available pairs before setting up your trading strategies.

Trading Fees

Tip: Visit HashKey's fee schedule for the most current rates and any VIP tier discounts.

Minimum Order Sizes

HashKey enforces minimum order values and precision limits. Orders below minimums or exceeding precision limits will be rejected:

Tip: Check HashKey for current minimum order sizes for specific pairs. SignalBee caches trading rules and handles precision automatically.

API Rate Limits

• HashKey enforces API rate limits to ensure fair access
• Rate limit errors (code -1003) are retryable after a short wait
• SignalBee handles rate limiting automatically
• If you see persistent rate limit errors, reduce your signal frequency

Warning: Continuing to send requests after rate limit errors can result in an IP ban (HTTP 418). SignalBee implements backoff to prevent this.

Testnet Available

HashKey offers a testnet environment for testing your integration before going live:

Tip: Use the testnet to verify your webhook configuration and signal delivery before enabling live trading. Contact HashKey for testnet credentials.

Time Synchronization

• HashKey uses Unix timestamps in milliseconds
• SignalBee synchronizes time automatically with HashKey servers
• Timestamp errors (-1021) indicate clock sync issues that SignalBee handles automatically

---

Troubleshooting

Common HashKey-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 HashKey status - Verify HashKey is not under maintenance
6. Check verification level - Some features require enhanced KYC

Orders Rejected?

If your orders are being rejected:

1. Check order type - HashKey only supports Market and Limit orders (no stops)
2. Verify minimum size - Order may be below minimum notional value
3. Check precision - Too many decimal places in quantity or price
4. Confirm pair exists - Verify the trading pair is available on HashKey
5. Check balance - Ensure sufficient funds for the order

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

---

Security Best Practices

Follow this checklist to keep your HashKey account secure:

HashKey Account Security

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

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

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 with same error code format