Exchange API key

This page explains how to securely connect your centralized exchange API keys to Sigrex. This allows the platform to execute trades on your behalf based on signal payloads.

---

🌐 Supported CEX-es

SpotFutures

Exchange	Type	Spot	Futures	More	API ID
Alpaca	CEX			No Paper trading	Spot: 1
Binance	CEX			USD-M only	Spot: 2 Futures: 3
Bitget	CEX			USD-M only	Spot: 13 Futures: 14
MEXC	CEX			USD-M only	Spot: 4 Futures: 16
Gate.io	CEX			USD-M only	Spot: 8 Futures: 9
Kraken	CEX				Spot: 6 Futures: 7
Hyperliquid	CEX			USDC only	Spot: 11 Futures: 12

📌 Only real/live trading accounts are supported for Alpaca. Paper trading keys are not allowed.

We are continuously working to expand Sigrex’s capabilities. More exchange integrations are planned for the future, including both centralized and decentralized platforms. Stay tuned!

---

🛠️ How to Connect an API Key

1. Name (Optional): You can assign a name to your API key connection to help identify it later. If left blank, the system will handle it.
2. Choose Exchange: Select which of the supported exchanges the API key is from.
3. Enter Keys:

   • Public Key (API key)
   • Private Key (Secret key)
   • Extra (if needed)
4. Validation: After submission, Sigrex sends a test request to the selected exchange to validate the API credentials and ensure the connection is functional.

---

⚠️ Important Notes

• Separate Connections for Spot & Futures: If you want to use the same exchange for both spot and futures trading, create two separate API connections—one for spot and one for futures.
• Alpaca Restrictions: We do not support paper trading keys from Alpaca. Please ensure your account is live before connecting.
• No Modification After Creation: After an API key connection is created, it cannot be edited for security reasons. If you need to change the keys or exchange:

  1. Disconnect it from all linked bots.
  2. Delete the connection.
  3. Create a new one with updated keys.

---

🔐 Security Notice

All API keys (public and private) are encrypted using strong server-side encryption and are only decrypted at runtime—when executing trades. Your keys are never exposed or stored in plaintext.