Weex Account Setup and API Integration: Complete Checklist for Automated Trading

Starting Without KYC: Weex’s Unique Entry Point

Weex stands apart by letting traders operate without identity verification—a significant advantage for privacy-focused traders. You can deposit crypto, use spot trading, trade futures, and make basic withdrawals without KYC, with the current non-KYC withdrawal limit of 10,000 USDT equivalent per day. This threshold is perfect for testing your automation setup and scalp strategies before committing to full verification.

However, for active traders planning sustained trading or larger positions, KYC completion unlocks 10x+ withdrawal capacity. Completing identity verification unlocks higher withdrawal limits and access to features such as WE-Launch. The process is straightforward: provide a photo ID (passport, driving license, national ID card) and a selfie; processing takes about 2 minutes. Note that you must download the Weex app and verify yourself there, as desktop-only verification is not supported.

Securing Your Account: 2FA Before Your First Deposit

Enable two-factor authentication immediately—before depositing any funds or generating API keys. Download a 2FA app like Google Authenticator or Authy; link the app to your Weex account by scanning the provided QR code; enter the 6-digit code generated by the app to activate 2FA.

This one step prevents account takeover even if your password is compromised. Go to the Profile section in the app, select Security Settings, and choose Enable 2FA and follow the prompts to link your account with an authentication app, such as Google Authenticator or Authy.

Critical recovery step: After enabling 2FA, immediately back up your recovery codes in a secure offline location. Unlike SMS-based 2FA, app-based authentication cannot be recovered if your phone is lost—there is no “forgot authenticator” flow. Without backups, a lost device means permanent account lockout.

Deposit Methods: Crypto vs. Fiat Trade-Offs

Weex supports multiple deposit methods including direct crypto wallet transfers, credit/debit card purchases, and P2P trading. For intermediate traders, crypto deposits are the fastest entry:

Weex does not charge deposit fees, but network fees may apply. The minimum is tiny: for Bitcoin it’s 0.00001 BTC ($1.17), Ethereum is 0.0000003 ETH ($0.001), and Tether is 0.001 USDT.

Fiat on-ramps exist but have regional limitations. Users can deposit funds using credit cards (Visa/Mastercard), Apple Pay, Google Pay, or direct bank transfers. Recent integration with OSL Pay, the dedicated payments division of OSL Group, a pioneering Hong Kong-listed digital asset company, specializes exclusively in fiat-to-crypto transactions, operating under its registration as a Virtual Asset Service Provider (VASP) in Italy.

For active traders: use crypto deposits to avoid fiat rails entirely. Copy your deposit address from Weex, transfer USDT or BTC from your existing exchange or wallet, and verify receipt before testing orders.

Wallet Connection: Bridge Balances Across Chains

Weex supports deposits on multiple blockchain networks, but network selection is critical. Always confirm the correct network before transferring; mismatched networks mean funds do not arrive automatically. Common networks include:

• TRC20 (Tron): Cheapest for USDT transfers; typically 1–2 USDT network fee
• ERC20 (Ethereum): Higher fees (~$5–$20 depending on gas) but widely supported
• BSC (Binance Smart Chain): Mid-range cost; fast confirmation

Click [Assets] > click [Deposit] > select the cryptocurrency you own to deposit into the platform; simply copy the deposit address provided or use the QR code to scan and deposit from any third-party digital wallet. Weex generates unique addresses per deposit session, reducing the risk of address reuse on public blockchains.

API Key Generation: Permission Scoping and IP Whitelisting

This is where active traders transition from manual to automated order flow. Weex supports API trading with both REST and WebSocket endpoints for automated market data access.

Step 1: Navigate to API Management

Log in to your account and navigate to the “Developer Settings,” “API Management,” or “Security” section; from there, you will typically find a button labeled “Create New Token” or “Generate API Key.”

Step 2: Create with Restricted Permissions

Minimum permission: if read-only solves the problem, do not enable trading; one purpose, one key. This means:

• Read-only key: Market data, balance queries, order history (no trading)
• Read + Trade key: Place and cancel orders (enables bots)
• Withdrawals: Rarely grant this; require manual confirmation instead

Start with read-only and test market data endpoints for 24 hours before granting trading permissions.

Step 3: Enable IP Whitelisting

For security reasons, we recommend linking an IP allowlist to your API key (max 10 IPs); separate multiple IP addresses with commas; for example: 192.168.1.213,192.168.1.214,192.168.1.215. Enable an IP whitelist; once bound, even a full leak of all three credentials fails from any other address — the request is rejected outright.

This is the single highest-value security control available. If your API key leaks, attackers cannot use it from a different IP.

Step 4: Passphrase Constraint

Weex requires the passphrase to be alphanumeric only — no special characters, a constraint that is not displayed prominently and is a common first-integration failure. Use a 16+ character alphanumeric passphrase (e.g., Weex2024SecureBot42) rather than a symbol-based password.

Step 5: Store Credentials Securely

You receive three credentials:

1. API Key: Public identifier for rate limiting
2. Secret Key: Private signing key (never share)
3. Passphrase: User-defined access phrase (cannot be recovered if lost)

If lost, the Passphrase cannot be recovered; losing any of these keys may result in asset loss. Store in an encrypted password manager (1Password, Bitwarden), not in code or version control.

API Rate Limits: Preventing Silent Failures During Volatility

There is rate limit for APIKey frequency; upon exceed client will get code 429: Too many requests; the account is used as the basic unit of speed limit for the endpoints that need to carry APIKey. The limit is 500 weight per 10 seconds for IP-based limits and 500 weight per 10 seconds for UID-based limits.

Common mistakes that trigger 429 errors:

• Polling order book every second without WebSocket (use streaming instead)
• Calling the same endpoint repeatedly across multiple threads
• Sending unthrottled market data requests during Bitcoin volatility spikes

API rate limit errors occur when you send too many requests too quickly, overwhelming the server; to avoid them, space out your queries and use efficient coding practices, ensuring smooth integration with platforms like Weex.

Recovery: If you hit a 429 error, back off for 30+ seconds before retrying. Use exponential backoff (1s, 2s, 4s, 8s) rather than hammering the endpoint.

Critical Setup Checklist: Avoid Repeated Errors

Use this checklist to catch common pitfalls before live trading:

1. 2FA Backup: Screenshot recovery codes; store offline
2. First Deposit: Send small test amount ($10–50) first; confirm arrival
3. API Key Creation: Use alphanumeric passphrase only; whitelist your server IP
4. Permission Test: Start with read-only; call /account endpoint and verify balance response
5. 15-Minute Wait: Newly created API keys take ~15 minutes to propagate globally; don’t assume “permission denied” means configuration is wrong
6. Withdrawal Address Whitelist: Before live trading, enable withdrawal address whitelisting so you can specify a list of trusted addresses to which you can withdraw funds; this prevents any withdrawals to unauthorized addresses, adding another layer of protection.
7. Test Market Data: Pull live prices via REST before enabling WebSocket streaming
8. Simulate Orders: Use Weex demo account or paper trading to verify order logic; test slippage handling

Connecting Your Bot: From REST to Live Execution

Once credentials are in place, connect your automation tool. Select “Weex,” enter any account name, paste the “API Key”, “API Secret”, “API passphrase” and click “Connect”.

For bots pulling live feeds, REST API suits on-demand requests; WebSocket API streams real-time data for faster decisions. Start with REST to validate logic, then migrate to WebSocket for sub-second latency.

Risk management before going live:

• Implement circuit breakers on slippage, spread width, and maximum order frequency; use exponential backoff on HTTP 429 rate limits and reconnect logic for WebSocket drops with sequence gap detection.
• Set position size limits in your bot config; never let the bot exceed manual order size
• Enable order confirmation logs; review first 10 filled orders manually

Completely automated workflows only become reliable after 48+ hours of live observation. Even with perfect setup, market conditions change; your bot’s assumptions may not.

Next Steps: Go Live on Weex

Once your account is secured with 2FA, funded via crypto deposit, and your API keys are whitelisted and permission-scoped, you’re ready to run automated workflows. These practices are standard across institution-grade API trading and are supported by the Weex account-level controls described in its documentation. Visit the Weex website to create your account and complete the setup checklist above.

---

👉 Ready to try it? Check the latest pricing and offer here.