Step-by-step guide to importing Bitget trade history into TradingAtlas via read-only API sync or CSV upload. Set up a read-only API key, fix common errors, and track PnL and taxes.
✓Transfer permission is not required for tax or analytics sync.
✓If the passphrase is forgotten, create a new API key.
Security best practices
✓Use a dedicated API key for TradingAtlas.
✓Enable IP whitelist if the exchange supports it and you have a stable IP.
✓Rotate keys periodically and delete keys you no longer use.
✓Never share API secrets in chat, email, screenshots, or support tickets.
What happens after import
Once your Bitget trades are imported, TradingAtlas builds an automated trading journal, calculates realized PnL and win rate, and prepares cost-basis data for tax reporting — all from the same normalized history.
Frequently asked questions
How do I import my Bitget trades into TradingAtlas?
Connect a read-only Bitget API key for automatic sync, or upload Bitget CSV exports (Spot trade history, Futures trade history, Funding / transaction records).
What Bitget API permissions do I need?
Read-only access only — Read. Never enable trading or withdrawal permissions.
Which Bitget CSV exports work?
Yes. Upload Bitget CSV exports — Spot trade history, Futures trade history, Funding / transaction records — and columns are detected and mapped automatically.
Are there any Bitget quirks I should know about?
Copy-trade fills appear alongside manual trades and must be treated as your own.
My Bitget import isn't working — what should I check?
A missing passphrase causes Bitget signature failures.
Is my Bitget data secure?
API keys are read-only and stored encrypted. TradingAtlas can never trade or withdraw from your account.
Import your Bitget trades now
Connect Bitget via read-only API or CSV and start tracking PnL and taxes.