How to Import Your Binance Trades

About importing from Binance

Quick facts

Connect Binance via API (recommended)

Create a read-only Binance API key so trades sync automatically.

1. 1Log in to Binance on the web.
2. 2Open your profile menu and select API Management.
3. 3Click Create API and choose System generated when prompted.
4. 4Name the key TradingAtlas or another recognizable label.
5. 5Complete email and 2FA verification.
6. 6In API restrictions, keep only Enable Reading enabled.
7. 7Leave Spot & Margin Trading, Futures, and Withdrawals disabled.
8. 8Optionally add an IP restriction if you have a stable IP.
9. 9Copy the API Key and Secret Key.
10. 10Paste both values into TradingAtlas, click Test, then Save Connection.

Required Binance API permissions

Read-only access is all TradingAtlas ever needs — never enable trading or withdrawals.

• ✓Enable Reading

Import Binance via CSV

Prefer files? CSV upload works for every account.

1. 1Open your Binance account and locate the trade history / statements export.
2. 2Export your full Binance trade history as CSV (export spot and futures history separately if they are split).
3. 3Export deposits, withdrawals, and fee records if provided separately.
4. 4Open TradingAtlas and go to Import → CSV.
5. 5Upload the Binance files — columns are detected and mapped automatically.
6. 6Review the normalized trades and confirm the import.

Binance CSV exports TradingAtlas reads

Upload any or all of these — they are merged into one timeline.

• ✓Spot trade history
• ✓USDⓈ-M futures trade history
• ✓COIN-M futures trade history
• ✓Transaction history (deposits, withdrawals, fees, converts)

Known Binance quirks

Platform-specific behavior that affects imports.

• ✓Spot, USDⓈ-M, and COIN-M each export in a different CSV schema.
• ✓Binance Convert trades often appear only in the transaction history, not the spot trade file.
• ✓API pagination limits mean very large accounts should sync in date ranges.

Common Binance import issues

Quick fixes for the problems traders hit most often.

• ✓If futures trades are missing, export the USDⓈ-M and COIN-M trade history separately — Binance keeps them in different files.
• ✓Signature errors usually mean the Secret Key was truncated or the wrong value was pasted.
• ✓Very large accounts should sync in date ranges to stay under Binance pagination limits.
• ✓Enabling trading permissions is unnecessary and increases risk.
• ✓Copying the wrong value into Secret Key causes signature errors.
• ✓Deleting or regenerating the Binance key requires updating TradingAtlas.

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

Frequently asked questions

How do I import my Binance trades into TradingAtlas?

Connect a read-only Binance API key for automatic sync, or upload Binance CSV exports (Spot trade history, USDⓈ-M futures trade history, COIN-M futures trade history).

What Binance API permissions do I need?

Read-only access only — Enable Reading. Never enable trading or withdrawal permissions.

Which Binance CSV exports work?

Yes. Upload Binance CSV exports — Spot trade history, USDⓈ-M futures trade history, COIN-M futures trade history, Transaction history (deposits, withdrawals, fees, converts) — and columns are detected and mapped automatically.

Are there any Binance quirks I should know about?

Spot, USDⓈ-M, and COIN-M each export in a different CSV schema.

My Binance import isn't working — what should I check?

If futures trades are missing, export the USDⓈ-M and COIN-M trade history separately — Binance keeps them in different files.

Is my Binance data secure?

API keys are read-only and stored encrypted. TradingAtlas can never trade or withdraw from your account.