How do I get my Binance API key?
API is the initially preferred method of integration.
If necessary, additional CSV files can be uploaded afterwards. When uploading CSV files, make sure to avoid transaction duplicates. More information on this can be found under CSV file upload.
- Log into your Binance account.
- Select API Management in the main navigation.
- Then click on Create Tax Report API.
Please note that only one Tax Report API key can be created. If you want to create a new one, you must first delete the existing API key and then edit the API key of your existing integration.
- Now enter your verification code (2FA) and confirm with Send.
- Leave all API restrictions (permissions) set to Enable Reading enabled by default.
- Copy your API key and your Secret.
Your Secret is now shown only once and available to copy! - To import your data, you must first create an Integration in the Blockpit Web App.
To do so, click + Integration in the upper navigation. - Select Binance from the list of exchanges, and then copy the API key and the secret into the designated fields. Confirm your entries by clicking Create.
Important
If you still use an old standard API and not the new Tax Report API, you can simply create one according to the instructions above. Then copy the new API key and the secret into your existing Blockpit Integration. How this works exactly, you can read here.
> How do I convert a Manual/CSV integration into a Synced Exchange/Wallet integration?
> Set a Start Date for your integration (Import Time Span)
Which data can be imported via Binance API?
Your complete transaction history always serves as the basis for your tax report. Preferably, automatic API solutions are used to import your transactions. Our team is committed to implementing all API data provided by your exchange for you.
Using the following list, you can identify all products that are implemented:
Transactions:
Due to the large product scope and limitations of the Binance API, there may be a delay of several hours or days in synchronizing your data.
Spot Market Trades older than 720 days (2 years) are not available via API and have to be imported manually or via XLS template.
USD-M Futures transactions older than 3 months are not available via API and have to be imported manually or via XLS template.
Supported
Crypto Deposits & Withdrawals
Fiat Deposits & Withdrawals
Fee Payments
Spot Market Trades
Leveraged Token Trades
Futures Trades P&L (Profit, Loss, Fee, Funding)
Buy Crypto (via Card/SEPA/etc.) (Fiat deposits must be added manually using the label "Non-Taxable In")
Direct Conversion
Dust to BNB Conversions (partially available)
Margin Trades & Loans (Cross & Isolated) (Loans & Repays imported as Unlabeled Deposit and Unlabeled Withdrawal - Label "Non-Taxable" applicable.)
Earn: Rewards & Distribution (Simple Earn, Locked Staking, Launchpad Claims, Launchpool, BNB Vault, etc.) (Locked Staking Rewards only available starting from 05.05.2021 via API - In addition, the
products listed below are not fully available).
ETH/BETH Staking (Locked) (For internal transfers from ETH into BETH staking, a Trade can be created manually to resolve mismatched balance tips).
In case of missing transactions, you can identify them in the history of your exchange and help our support team via ticket to include them in our import spectrum.
Not Supported
Auto-Invest
Dual-Invest (Withdrawals on subscription date must be created manually.)
Liquid Swaps
Liquidity Farming
Binance Pool Mining
BNSOL - APR Boost Airdrop Reward Claims
Binance Card/Pay/Gift
Referral Bounties
Trading Bots
Block Trading
OTC Trades (P2P)
Crypto Loans
Auto-Conversions
NFTs
Caution
Binance does not provide data for delisted assets and trading pairs via API.
Missing transactions can be found by comparing the actual history of your exchange. You can then add these directly to your Blockpit Integration by subsequently uploading your CSV file (see below) or by migrating your CSV data to our Blockpit Excel Template.
How do I get my Binance CSV file?
-
The following steps will help you to download your Binance CSV file and import it into your Blockpit Integration:
- Log into your Binance account.
- Select Transaction History in the main navigation.
- Then click on the icon shown below and select Export Transaction Records.
- Then select Customize to enter the relevant transaction periods (preferably whole tax years from 01.01 to 31.12).
- As soon as the file has been generated by Binance, you can download it. We also recommend naming the file after the corresponding transaction period. (Example: Binance history 2020-01-01 - 2020-12-31)
- You can now upload the file to your Blockpit Integration in the Dashboard. To do this, click on Edit / Upload CSV in the Integrations tab as shown below.
- Now drag the corresponding file(s) into the field displayed below and confirm your entry with Save to upload your transactions.
When uploading your transactions into your Binance Integration, the system does not check for transaction duplicates.
Transactions that already exist in your Integration must therefore be removed from the CSV file before uploading.
Synced Balance:
Supported
All Account Balances
Mismatched
Launchpool
Liquid Swap Shares
If your assets are not locked in the Spot Wallet, but in the Launchpool, they will not be displayed in their entirety in the Synced Balance of your Blockpit integration (until reflow). However, this has no effect on the tax report, as no outflows (transactions) happen internally in your Binance Integration.
If your Synced Balance is displayed incompletely, you can help our support team via ticket to include it in our import spectrum (if technically possible).
> What is the difference between Synced/Manual Integrations and Synced/Calculated Balance?
How do I solve problems with my Binance Integration?
-
Blockpit shows different Tips (indicators) in the Dashboard and your Transactions list depending on the type of problem you are facing. The following procedure can help you to solve these problems.
Please always synchronize all your integrations first using “Synce All” (Dashboard) and then start a calculation of your transaction data using “Recalculate ” (Transactions) before you analyze Tips or the performance values of your portfolio.
Product updates provided by Blockpit have no direct effect on existing transaction data in your Integration (precautionary measure to avoid changing existing transaction histories through automatic product updates), so creating a new Integration could bring it up to date and solve your problem (Tips) already.
1. Create a new Integration
Temporarily create a second Integration to be able to compare the new and old Integration. Then delete the Integration that you do not want to keep.
> How to create, sync, edit, convert, group, delete and deactivate Integrations?
Alternatively, it is possible to re-synchronize missing or incorrectly imported transactions. In order not to damage existing transaction histories and to avoid new duplicate transactions, we recommend the following article:
> How can to synchronize integrations or re-synchronize missing/incorrectly imported transactions?2. Label or merge Unlabeled Transactions
Unlabeled transactions can be subsequently categorized with a corresponding label, edited or merged into Trades or Transfers by selecting related transaction pairs. It is also possible to change the labels of multiple similar transactions collectively (bulk edit).
> Basics on Labeling and Merging of Transactions
3. Manually edit, exclude or delete transactions
If you should still see Tips, it is possible that these were caused by incorrect transactions or transactions that were imported twice. These transactions can be edited as follows.
> Transaction Details Overview and Managing & Editing of Transactions
4. Add new transactions
If your transaction history has not been fully imported, you can add transactions manually or upload them directly via CSV file upload into your Blockpit Integration. Alternatively, you can also migrate your CSV data to our Blockpit Excel Template.
> CSV file upload: Subsequently import missing transactions directly via Binance CSV file
> Alternative migration of your CSV data to our Blockpit Excel Template
Tip: If you are unable to create an Integration without "Mismatched Balances" using an initial API integration and additional CSV uploads, try creating a CSV Integration first and then convert your Integration into an API Integration afterwards. In addition, use a current import status date (e.g. import time span: today's date) as a separator to avoid transaction duplicates.
> How do I convert a Manual/CSV integration into a Synced Exchange/Wallet integration?
> Set a Start Date for your integration (Import Time Span)
5. Continue to browse Troubleshooting category> Overview of frequently asked questions and their solutions