If your API integration shows a tip, usually transactions are missing, or they were imported incompletely or twice. Work through the steps below in order. Often the problem is already solved after step 1.
ℹ️ Before you start: First sync all integrations with 🟩 Sync All in the Dashboard (Integrations tab), then start 🟧 Calculation in the sidebar. Only then do tips and portfolio values show the current state.
You see … | Start at |
Mismatched Balance (Dashboard) | Step 1, then 4 |
Missing History | Step 1, then 3 and 4 |
Unlabeled | Step 2 |
Duplicate transactions | Step 3 |
1. Create the integration again
Matching tips: Mismatched Balance (in the Dashboard) and Missing History (in the transactions).
When Blockpit improves an integration, transactions you have already imported do not change. This keeps existing histories stable. A newly created integration, however, uses the current detection and often solves the problem already.
To do this, temporarily create a second integration for the same source and compare both. Afterwards, keep only the better one.
⚠️ Caution: If you delete an integration, all of its transactions disappear too, including your changes (labels, merges, notes). Only delete the integration you have not edited.
Instead of creating a new one, you can also re-sync missing or incorrectly imported transactions. Read the precautions beforehand so that no duplicates appear.
2. Label or connect transactions
Matching tip: Unlabeled (In/Out).
You can categorize unlabeled transactions afterwards, edit them, or connect matching pairs into a Trade or Transfer (merge). You change several similar transactions at once with a bulk edit.
3. Edit or delete transactions
If tips remain, incorrect or duplicate imported transactions are often the cause. You edit or delete them via the three-dot menu of the transaction in Transactions:
ℹ️ Good to know: You find transactions you deleted in the normal way with the filter View › Status: Deleted and can restore them there.
4. Add missing transactions
If transactions are missing, add them one by one or upload them afterwards: directly as your exchange's CSV file if the integration supports it (stated in its guide), or with the Blockpit Excel template.
💡 Tip: If you cannot get an integration without Mismatched Balance with API and an additional CSV upload, reverse the order: first create a CSV integration and then convert it into an API integration. Set a current import start date (for example today's date) as the separation point so that no duplicates appear.
Typical mistakes
✗ Forgetting read-only permission, or allowing trading/withdrawal → import incomplete or an unnecessary security risk; the API key only needs read access
✗ Importing the same period via API and CSV → duplicates; set a start date as the separation point
✗ Deleting the old integration before the new one has fully synced → labels and merges of the old integration are gone
5. More help
👁🗨 For more help with balance mismatches, missing transactions or incomplete histories, we recommend our Blockpit Expert Support (DE / AT / CH).
Our Expert Support is the complete solution for your data: our experts take over the individual analysis of your account and support you with the entire data preparation – from clarifying mismatches in your balance/holdings and entering historical data into the Excel template, through cleaning faulty CSV files, to the reconstruction of closed exchanges and the full import directly into your Blockpit account.
👉 Simply book your free 15-minute initial call under Expert Service (usable even without buying a package beforehand) to discuss your individual needs and effort without obligation.
🛠️ Technical error in the integration?
If there is demonstrably a technical error, for example an incomplete Synced Balance despite correct setup, or a connection error that persists, write to us in the chat. Support will gladly look into it.