**TL;DR **To ensure complete and accurate Binance.com imports, use both API and CSV methods. API imports offer automation, while CSV helps fill in gaps. Certain data types like Margin PnL, Earn, and some derivatives are not fully supported, so any missing transactions from the API import need to be added manually. Historical data before September 2022 is not available via API. After importing, run the ValiChecks to catch any warnings or errors in your account.
How can I import Binance.com transactions into CoinTracking?
Binance.com imports are best handled with a combination of API and CSV methods. This ensures a complete dataset because of certain limitations in both sources.
Since neither method covers 100% of transaction types on its own, always check your account afterwards with ValiChecks (Analysis > ValiChecks) to identify missing data, duplicates, or other warnings that need manual correction.
How do I set up the Binance.com API import?
What do I do if I get an API key error?
If the API import fails with a key error during the initial setup, the API job and the API key itself usually need to be recreated from scratch. Steps:
Delete the existing API job in CoinTracking
Delete (or revoke) the existing API key on Binance.com
Create a brand-new API key on Binance.com
Set up a new API import job in CoinTracking using the new key
Simply retrying with the same key/job usually does not resolve this error.
How do I import Binance.com CSV files?
Important Notes:
Binance.com only allows 6 CSV exports per month
Always run the API import first, then CSV
CSV is essential for data types not covered by the API
Large files may take time to process
During the CSV import, pay close attention to the slider setting. Choosing the wrong option can lead to duplicate imports or import errors. Make sure the slider matches the type of data/date range you're importing before confirming.
What are the current Binance.com import limitations?
Due to changes in Binance.com data availability and formatting, not all transaction types are currently supported. Here are the known limitations:
Not imported via API or CSV:
Margin PnL
Leveraged Tokens
Battle
Earn (partly)
Savings and Staking (partly)
Launchpad (partly)
Liquid Swap
Dual Investment (partly)
Pool Savings
Auto-Invest
Binance.com Visa Card
Crypto Loans
Binance.com Pay
Recurring Buy
NFT trades
Gaming / IGO
Mystery Boxes
Since the API does not cover these transaction types (and CSV export limits may also leave gaps), any missing transactions will need to be added manually in CoinTracking to keep your portfolio and tax report accurate.
Additional notes:
"Dust to BNB":
API only fetches the last 100 transactions
CSV includes all but may have minor rounding differences
CSV files often exclude withdrawal fees
Binance.com API no longer offers historical trades before September 2022
How do I update my Binance.com API trade pairs?
If you trade a new coin pair not previously seen in your Binance.com API job, follow these steps:
Go to the Binance.com API Import Page
Click Edit on your Binance.com job
Click Update Job and Trade Pairs
This will trigger the import of all new trade pairs and related BNB fee data.
How do I import Binance.com Futures trades?
Binance.com offers two CSV formats for Futures data:
Trade History File
- Import as Deposit and Withdrawal, then change transaction type to Futures Profit or Futures Loss using bulk edit
Transaction History File
Import three times using settings for:
COMMISSION, INSURANCE_CLEAR, REALIZED_PNL
TRANSFER
FUNDING_FEE
Each step can be simplified by importing pre-configured .dat files from CoinTracking.
What about Launchpad Lottery Tickets?
Binance.com does not provide BNB expenditure for Launchpad tickets via API. You can:
Import the coin reward as Income
Manually enter the BNB spent as Spend
Or replace Income with Trade and enter the BNB value under Sell
Each method has different tax implications, so choose based on your reporting needs.
How do I do a final check after importing?
After completing both API and CSV imports, run ValiChecks (Analysis > ValiChecks) to review your account for warnings, errors, missing balances, or negative balances. This helps catch any remaining gaps caused by the import limitations listed above, so you can correct them manually before generating tax reports.