Missing transactions after connecting an exchange API
If you have connected your exchange account via API and some transactions are missing, the most common causes are incorrect API permission settings, date range filters, or the API not supporting certain transaction types. You need to verify API scopes, check exchange-side export options, and reconcile with manual records to identify what is missing.
Why transactions might not appear
APIs are not perfect mirrors of exchange activity. They often have limitations on what data they serve, how far back they go, and how frequently they update. The first step is understanding which transactions your exchange API can access.
Common API Limitations
- Historical depth: Many exchange APIs only return the last 90 days of trades or deposits. Older transactions may not be retrievable through the API at all.
- Transaction type coverage: Some APIs exclude certain events, such as airdrops, staking rewards, or margin liquidations. Check your exchange’s API documentation for a complete list of supported endpoints.
- Rate limits: If you connect multiple portfolio trackers or run frequent syncs, you may hit rate limits, causing the API to return incomplete data. This can look like missing transactions, especially during high-volume periods.
Step-by-Step Troubleshooting
1. verify API permissions
Most exchange APIs require specific permissions (scopes) to read different data categories. Common scopes include: - Read trade history - Read deposit/withdrawal history - Read balance - Read staking or rewards
If you only granted “read balance” permission, the API may return your current holdings but not individual transactions. Revisit your exchange’s API management page and ensure the correct scopes are enabled. Some exchanges require separate API keys for trading versus history endpoints.
2. check date range settings
Many portfolio trackers let you set a start date for API syncs. If this date is too recent, older transactions will be missing. Look for a “sync from” or “import date range” setting in your tracker’s exchange connection configuration. Set it to the earliest possible date (often “all time” or a specific date when you started using the exchange).
3. Confirm the API Supports the Transaction Types You Need
Different exchanges expose different data through their APIs. For example: - Some exchanges only include spot trades in the API, excluding futures or margin trades. - Staking rewards, referral bonuses, and airdrops may only be available through a separate rewards API endpoint or not at all. - Deposits and withdrawals may be on a different endpoint from trades.
Check your exchange’s API documentation or contact their support to confirm which endpoints cover your missing transaction types. If the API does not support them, you will need to export those transactions manually via CSV and import them separately.
4. Compare Against a Manual Export
Export a CSV of your full transaction history from the exchange’s web interface (covering the same date range). Compare the CSV rows to the transactions your tracker received via API. Look for patterns: - Are all trades missing, or only specific types? - Are deposits and withdrawals present but trades absent? - Are transactions from a particular date range missing?
This comparison will tell you exactly which data the API failed to retrieve.
When the API Cannot Provide the Data
If you confirm the API lacks the necessary endpoints, you have two options:
- Manual CSV import: Download the missing transaction history from the exchange and import it manually into your tracker. Be aware of duplicate risk - most trackers detect duplicates by transaction ID, but you may need to verify.
- Use a different exchange or aggregator: Some portfolio trackers support multiple exchanges or aggregator services that pull data from additional endpoints. Switching to a tracker that supports your specific exchange’s advanced API might resolve the issue.
Preventing future missing transactions
- Set a conservative sync start date: When first connecting an exchange, set the sync date to the earliest possible date to capture all history. After the initial sync, future syncs will only pull new transactions.
- Monitor API rate limits: If you run multiple syncs per day, check the exchange’s rate limit policy. Some exchanges reset limits hourly or daily.
- Keep manual backups: Even with a working API, periodically export your transaction history as CSV files and store them locally. This protects against API changes, exchange shutdowns, or data loss.
When to contact support
If you have checked permissions, date ranges, and transaction type coverage, and transactions are still missing, contact the portfolio tracker’s support team. Provide: - Your exchange name - Which specific transactions are missing (e.g., “all trades from August 2024” or “staking rewards from October 2025”) - Screenshots of your API permission settings - A comparison showing the CSV export has the data but the API import does not
The tracker’s support may identify a bug or configuration issue you missed.
Missing transactions after an API connection are usually fixable. The process is systematic: check permissions, confirm date ranges, verify transaction type support, and compare against a manual export. If the API cannot provide the data, fall back to manual CSV import and adjust your long-term tracking setup to include regular backups.
Not financial advice. venko.tech publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.