Binance.com Import Overview and Restrictions
TLDR: 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, and even a working API connection will not cover all Binance activity. Historical data before September 2022 is not available via API, and API imports require a paid CoinTracking plan. A manual import option is also available if gaps remain.
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. If you still end up with missing transactions after using API and CSV, a manual import is also possible (see below).
Do I need a paid plan to use the Binance.com API import?
Yes. API imports (for Binance.com and other exchanges) are not available on the Free plan. You need to upgrade your CoinTracking account to a paid plan to set up and run an API import job.
How do I set up the Binance.com API import?
Note on the Start Date field: If you set a Start Date when creating or editing your Binance.com API job, CoinTracking will not import any transactions dated before that Start Date. Only use this field intentionally (for example, when you've already accounted for older transactions manually). Otherwise you may end up with missing history.
Keep in mind that even with the API connected and working correctly, Binance.com does not provide complete transaction data for every activity type (see limitations below). CSV import and, in some cases, manual entry are still needed to fill the gaps.
How do I import Binance.com CSV files?
Is there a way to import Binance.com data manually?
If API and CSV imports still leave gaps in your Binance.com history, CoinTracking also provides a manual import guide for Binance.com. This lets you enter missing transactions (for example, unsupported product types) directly, as an alternative or supplement to the automated import methods.
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
API import requires a paid CoinTracking plan
Setting a Start Date in the API job blocks import of anything earlier. Use with care
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. This applies even when the API is active and running correctly. Binance simply does not expose complete data for every product. 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
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
For data types that Binance doesn't expose at all, use CSV or the manual import guide instead
How do I compress or summarize a large number of Staking/Earn transactions from Binance.com?
Binance.com Earn and Staking rewards are often paid out in many small, frequent transactions, which can clutter your transaction list. To consolidate them:
Delete the existing Staking/Earn transactions for the period you want to summarize (filter by exchange and transaction type in your transaction list, then bulk delete).
Add up the total reward amount for that period.
Manually enter a single summarized transaction (e.g. as Income) with that total amount, using a date within the period you deleted.
Open your Binance.com API job and set the Start Date to the date of your summarized entry (or later), so the API does not re-import and duplicate the same period going forward.
Important: Setting a Start Date blocks import of anything earlier than that date. Only do this after you've manually accounted for the older transactions.
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.
I'm getting a CloudFront 504 error during the Binance.com API import. What should I do?
A CloudFront 504 error usually points to a temporary issue on Binance's side (Binance's API infrastructure runs behind CloudFront, and can occasionally time out). If you see this error:
Wait a few minutes and try the import again
If the error keeps happening, try removing and recreating the API job
If it still persists, contact support so the connection can be checked further