How to Import Your Bybit Trades

About importing from Bybit

Quick facts

Connect Bybit via API (recommended)

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

1. 1Log in to Bybit on the web.
2. 2Open the profile icon and go to API.
3. 3Click Create New Key.
4. 4Choose System-generated API Keys.
5. 5Select API Transaction as the key usage if Bybit asks for a use case.
6. 6Set permissions to Read-Only.
7. 7Enable the read permissions needed for wallet, orders, positions, and trade history.
8. 8Do not enable read-write, transfer, or withdrawal permissions.
9. 9Optionally set an IP restriction.
10. 10Complete 2FA verification.
11. 11Copy the API Key and API Secret.
12. 12Paste both values into TradingAtlas, click Test, then Save Connection.

Required Bybit API permissions

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

• ✓Wallet: Read
• ✓Orders: Read
• ✓Positions: Read
• ✓Trade History: Read

Import Bybit via CSV

Prefer files? CSV upload works for every account.

1. 1Open your Bybit account and locate the trade history / statements export.
2. 2Export your full Bybit 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 Bybit files — columns are detected and mapped automatically.
6. 6Review the normalized trades and confirm the import.

Bybit CSV exports TradingAtlas reads

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

• ✓Closed PnL (derivatives)
• ✓Transaction log (funding, fees)
• ✓Spot trade history

Known Bybit quirks

Platform-specific behavior that affects imports.

• ✓Closed PnL and the transaction log are separate exports — both are needed for complete derivatives history.
• ✓Inverse contracts are settled in the base coin and need contract-aware PnL.
• ✓API keys can only be created on the website, and new accounts may wait 48 hours.

Common Bybit import issues

Quick fixes for the problems traders hit most often.

• ✓API keys can only be created on the Bybit website, not the mobile app.
• ✓New accounts may be blocked from creating API keys for the first 48 hours.
• ✓For complete history, export both Closed PnL and the transaction log.
• ✓Creating the key in the mobile app is not supported by Bybit.
• ✓Selecting Read-Write instead of Read-Only is not required.
• ✓New accounts may need to wait before API creation is available.

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 Bybit trades into TradingAtlas?

Connect a read-only Bybit API key for automatic sync, or upload Bybit CSV exports (Closed PnL (derivatives), Transaction log (funding, fees), Spot trade history).

What Bybit API permissions do I need?

Read-only access only — Wallet: Read, Orders: Read, Positions: Read, Trade History: Read. Never enable trading or withdrawal permissions.

Which Bybit CSV exports work?

Yes. Upload Bybit CSV exports — Closed PnL (derivatives), Transaction log (funding, fees), Spot trade history — and columns are detected and mapped automatically.

Are there any Bybit quirks I should know about?

Closed PnL and the transaction log are separate exports — both are needed for complete derivatives history.

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

API keys can only be created on the Bybit website, not the mobile app.

Is my Bybit data secure?

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