API Import or CSV Upload: Which Crypto Tax Workflow Fits You?

Overview

Before you can prepare a crypto tax report, you need transaction data. Two common ways to bring that data into a tax workflow are:

• connecting an exchange through an API key; or
• uploading a CSV file exported from the exchange.

Both methods can be useful. They are not equally reliable in every situation.

CryptoTaxBridge provides both import types, but current support differs: API import is available for several exchanges, while the current CSV upload option in the application is available for Binance. Understanding the difference helps you choose the right starting point and avoid treating an incomplete file as a finished tax record.

What Is an API Import?

An API import connects CryptoTaxBridge to an exchange using credentials created for accessing account history. In a safe tax-reporting workflow, those credentials are read-only: they permit retrieval of relevant transaction information but do not permit trades or withdrawals.

API import is useful because it can reduce repetitive manual downloads and support later synchronisation of transaction history. It can also retrieve categories of exchange activity that are easy to miss when a user selects the wrong export file.

In CryptoTaxBridge, the API import interface currently exposes:

• Binance;
• Bybit;
• Coinbase;
• Crypto.com Exchange;
• Gate.io;
• Kraken;
• OKX.

The exact history available depends on each exchange API and your permissions.

What Is a CSV Upload?

A CSV upload uses a file exported from an exchange and provided manually to the application. It can be helpful when:

• you do not want to maintain an API connection;
• an old account is no longer actively used;
• you already have the correct historical export;
• API history is unavailable or limited for a particular situation.

But CSV import is not automatically complete. Exchanges may provide several different CSV export types, each covering only certain activity. A file called “account statement” may not contain the trade history required for a tax calculation.

In the current CryptoTaxBridge interface, CSV upload is available for Binance. The application warns that a Binance Account Statement CSV may contain deposits, withdrawals, and transfers while missing or misrepresenting Spot, Margin, Convert, or Futures trading history.

Import exchange transactions

Comparing the Two Workflows

Consideration	API Import	CSV Upload
Setup	Requires read-only API credentials	Requires the correct exported file
Updates	Designed for syncing imported history	Requires new uploads when data changes
Completeness	Depends on exchange endpoints and permissions	Depends on the export type selected
Security	Must use read-only permissions	File contains sensitive financial history
Best use	Active accounts and ongoing tracking	Historical or manual record imports

Neither method removes the need to review data. API access can be incomplete if permissions or exchange endpoints are limited. CSV files can be incomplete if the wrong export was downloaded. The correct question is not “Which method is perfect?” but “Which method gives me the complete, verifiable history required for this report?”

When API Import Is the Better Choice

API import is usually the stronger starting point when you:

• actively trade on a supported exchange;
• intend to update records over time;
• have multiple categories of activity to capture;
• want to avoid repeated manual exports;
• can create strictly read-only credentials.

The security rule is non-negotiable: a tax import should never require trading or withdrawal permissions. Where the exchange provides permission controls, grant only the read access needed for history.

When CSV Upload Makes Sense

CSV upload can be sensible when:

• you are importing a fixed historical period;
• you prefer not to create an API key;
• you can confirm the file contains the required transaction categories;
• you are prepared to upload updated files when necessary.

For Binance data in particular, do not assume that an account statement is equivalent to full trade history. Read what the export contains and verify that all relevant trade categories are accounted for before relying on a tax calculation.

The Multi-Exchange Problem

Many portfolios cannot be reconstructed from one import source. You might buy on Coinbase, move assets to a wallet, trade on Kraken, and later dispose of holdings on Binance.

Whether you choose API or CSV for each source, you must still collect a continuous history. Watch for:

• deposits without matching acquisitions;
• withdrawals without known destinations;
• transfers mistakenly treated as disposals;
• sales for which no acquisition source is present;
• duplicated history imported through overlapping sources.

A tax report is not improved by adding more data blindly. It is improved by adding the right data and reviewing how it connects.

Start transaction tracking

Country Rules Still Decide the Report

Import method controls how data reaches the system. It does not decide how the tax report is calculated.

CryptoTaxBridge currently supports reporting workflows for the United Kingdom, United States, Netherlands, Ireland, Australia, and Canada. Each country requires its own logic and reporting focus:

• UK: same-day and 30-day matching, followed by Section 104 pooling;
• US: FIFO capital gains support with short-term and long-term separation;
• Netherlands: Box 3 support information;
• Ireland: CGT support calculations in euro;
• Australia: CGT support with eligible individual discount treatment;
• Canada: pooled adjusted cost base under a capital-account assumption.

The correct workflow is: gather complete data, then calculate according to the correct country.

A Practical Decision Rule

Use this simple rule:

• choose API import for supported active exchange accounts when you can safely create read-only credentials;
• choose CSV upload where a supported and complete export is available and manual import suits the account;
• do not generate a report until all material exchanges and wallets have been reviewed.

Conclusion

API imports and CSV uploads are not competitors so much as tools for different situations. API access is often better for ongoing tracking; CSV files can be useful for historical or manual workflows. Both require care, security, and review.

What matters at filing time is not the import method you preferred. It is whether your transaction history is complete, your transfers are understood, and your country-specific calculation is supported by evidence.

Prepare tax report

This article describes current CryptoTaxBridge import options as of June 2026. Exchange support and available import methods may change as the product develops.