Bitvavo partners with Blockpit.
How do I get my Bitvavo 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 Bitvavo account.
- Click in the top-right corner on your profile button and select API.
- Click on Request new API key and enter a name for your API key.
- Now grant the API key permission for "View information" and keep all other permission disabled as shown in the image below.
- Do not use IP whitelisting for now.
- Now finish by entering your 2FA Code followed by Confirm.
- You will now receive an API key confirmation mail.
Click the link in the mail to activate your API key before moving on to the next step.
- Your API key and Secret are now visible in the API-List.
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 Bitvavo from the list of exchanges, and then copy the API key and the Secret into the designated fields. Confirm your entries by clicking Create and finish the setup on Bitavo by clicking Confirm.
> 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 Bitvavo 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:
Supported
Deposits & Withdrawals
Fee Payments
Spot Market Trades
Staking
Airdrops
Affiliate Rewards
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
Remove Dust
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 Bitvavo CSV file?
-
The following steps will help you to download your Bitvavo CSV file and import it into your Blockpit Integration:
- Log into your Bitvavo account.
- Go to Transaction history via the profile menu.
- Next click on Export.
- Select Full History or a specific time period and then click Export to download the file.
- 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 Bitvavo 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.
Syned Balance:
Complete import scope
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 Bitvavo 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 Bitvavo 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 start 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