Connecting Exchanges
TrynQuant uses CCXT (CryptoCurrency eXchange Trading Library) to connect to 100+ exchanges via a unified API. You connect by providing an API key and secret from your exchange account.
API Key Security
Always restrict your API key permissions to Read and Trade only. Never grant withdrawal permissions to any third-party service including TrynQuant. This ensures that even in the unlikely event of a key compromise, funds cannot be moved off the exchange.
Supported Exchanges
TrynQuant supports all exchanges available through CCXT. Popular options include:
Support for a specific exchange depends on CCXT's implementation. Some exchanges have limited feature support (e.g. futures-only or no websocket feeds).
How to Generate API Keys
Each exchange has a slightly different UI, but the general process is the same:
Log in to your exchange account
Navigate to Account → API Management (or similar — check your exchange's help docs)
Click "Create API Key" or "Generate New Key"
Give the key a label (e.g. "TrynQuant")
Set permissions: enable Read and Trade. Disable Withdrawal and Transfer
Set an IP whitelist if the exchange supports it (optional but recommended)
Copy the API Key and Secret — the secret is shown only once
If the exchange requires a passphrase (e.g. OKX, Bitget), create one and note it down
Required Permissions
View balances, open orders, order history, and market data. Always required.
Place and cancel orders. Required for any bot that executes trades.
Move funds off the exchange. NEVER grant this to TrynQuant or any trading bot.
Passphrase Exchanges
Some exchanges including OKX and Bitget require an additional API passphrase when creating a key. This is a user-defined string you set at key creation time. The TrynQuant form shows a passphrase field for exchanges that require it — enter the exact value you used when creating the key.
Testnet Mode
Some exchanges offer a testnet (sandbox or demo trading) — a simulated environment where you can place real API calls with fake funds. Notable examples include Bybit Testnet and Binance Testnet.
When adding a connection in TrynQuant, look for the Testnettoggle. Testnet connections use separate API keys issued by the exchange's testnet platform — they are not the same keys as your live account.
Bybit: Three Trading Environments
🟢 Live
Production trading. Uses your regular Bybit API keys. Connects to api.bybit.com.
🟡 Demo Trading
Uses your regular Bybit API keys but with a simulated balance. Connects to api-demo.bybit.com. Great for testing bots.
🧪 Testnet
Requires a separate Bybit Testnet account at testnet.bybit.com with its own API keys. Connects to api-testnet.bybit.com.
Note: Paper trading on TrynQuant (real-time prices with simulated fills) is different from exchange testnet. Paper trading is recommended over testnet for most users as it requires no additional API setup.
RSA Key Authentication
Some exchanges support — or require — RSA key-pair authenticationas an alternative to HMAC-SHA256 secrets. Instead of a shared secret, you generate a public/private keypair: the public key is registered on the exchange, and your private key is stored encrypted in TrynQuant's vault.
Bybit — RSA Key Setup
Bybit supports RSA key-pair authentication for all account types. When creating an API key on Bybit, select “Self-generated API keys (RSA)”. You must provide a public key — Bybit does not generate the keypair for you.
- 1Log in to Bybit → Account & Security → API Management.
- 2Click "Create New Key" → choose "Self-generated API keys".
- 3Select RSA as the authentication method.
- 4Use the generator below to create a 4096-bit keypair.
- 5Copy the PUBLIC key and paste it into the Bybit API key form.
- 6Confirm key creation. Save the PRIVATE key (download .pem).
- 7Go to Dashboard → API Keys → Add Exchange → select Bybit.
- 8Upload your private key .pem in the RSA Private Key field.
RSA-4096 Key Generator
BybitGenerate a cryptographic key pair entirely in your browser — your private key never leaves your device until you explicitly upload it below.
Coinbase Advanced — RSA Key Setup
Coinbase Advanced Trade API requires RSA or EC key-pair authentication — HMAC secrets are not supported for new keys.
- 1Log in to Coinbase Advanced → Settings → API.
- 2Click "New API Key" → choose "Self-managed (Advanced)".
- 3Select RSA authentication.
- 4Use the generator below to create a 4096-bit keypair.
- 5Copy the PUBLIC key and paste it into the Coinbase API setup.
- 6Complete 2FA verification. Store the PRIVATE key securely.
- 7Go to Dashboard → API Keys → Add Exchange → select Coinbase Advanced.
- 8Upload your private key .pem in the RSA Private Key field.
RSA-4096 Key Generator
Coinbase AdvancedGenerate a cryptographic key pair entirely in your browser — your private key never leaves your device until you explicitly upload it below.
Adding a Connection in the Dashboard
- Go to Dashboard → API Keys
- Click "Add Exchange"
- Select your exchange from the dropdown
- Enter your API Key, Secret, and Passphrase (if required)
- Click "Test Connection" — TrynQuant will verify the keys are valid
- If successful, the exchange appears in your connections list