Read-only API keys for trade import — what to enable
How to connect an exchange to the journal without granting trade or withdraw permissions — and why TradaxLab checks before saving.
By TradaxLab
Least privilege is the feature
Create an API key with read/history permissions only. Turn off spot/futures trading and withdrawals. IP-restrict if your exchange allows it.
TradaxLab probes key permissions before storing credentials and encrypts secrets server-side. If the key can trade, we reject it.
Live vs beta venues
Binance and Bybit use the live sync path. Additional venues connect in beta via CCXT from Settings → Exchanges — same read-only rule.
After the first sync
Tag imported fills with setup and playbook. Raw fills alone don’t improve process — the tags do.
Permission checklist before saving a key
Enabled: read balances, read order/trade history.
Disabled: spot/futures trading, withdrawals, transfers, key management.
Optional: IP whitelist and key label by environment (live/test).