Reconstruct Exchange Data

Reconstruct Exchange History
Binance, Kraken & Co.

MEXC, Bybit, Kucoin or a closed exchange? Retrieving historical data retroactively is the real challenge. TX-Partner combines API, CSV and manual processing.

Free Documentation Check

Initial assessment of your exchange data · 30 min.

View all services
Exchange Documentation in Numbers

Most exchange connections fail not because of the tool, but because of the data:

12 Mo.
Typical API Limit
Most exchanges only deliver complete data going back 12 months via API
API + CSV
Combination Required
For Binance, MEXC, Bybit, Kucoin and Gate.io the API alone is not enough
Manual
Often Unavoidable
Tax tools cannot read CSV files from many exchanges. Manual processing is required
The Problem

Why CSV Exports Alone Are Not Enough

Reconstructing exchange history retroactively requires more than a CSV export. API limits, deleted accounts and missing time periods make professional reconstruction necessary.

01_API_LIMITS

API Doesn't Cover All Products

For exchanges like Binance, the API doesn't cover all products: Spot, Earn, Staking and Futures run on different endpoints and often have gaps in historical data. CSV exports fill those gaps, but need to be correctly merged with API data to avoid duplicates.

02_EXCHANGE_CLOSED

Exchanges Closed, Accounts Gone

FTX, Bittrex, Cryptopia, Celsius, MT.GOX: Closed exchanges no longer provide CSV exports. Coinbase Pro (legacy) and Bitpanda Pro also no longer exist in their original form.

03_COST_BASIS

Missing Cost Basis = Phantom Gains

Without complete exchange history, the tax tool sets the acquisition cost to 0 EUR. The result: phantom gains, negative balances, and an inflated tax liability.

Exchange Overview

Not Every Exchange Is the Same

Different exchanges require different strategies. Some deliver clean data, others require significant manual post-processing.

Important: This overview refers to historical data. For ongoing tracking, most exchanges work well. Problems arise when transaction data needs to be retrieved retroactively.

Historically Often Problematic

Historical data often requires matching API and CSV or completely manual processing.

Binance API + CSV sync required
Kucoin Often API + CSV matching
Gate.io Often API + CSV matching
OKX Often API + CSV matching
BingX Often API + CSV matching
MEXC API severely limited
Bybit CSV supplement needed
Crypto.com Multiple export types
Bitvavo Migration to Hyphe
Coinbase Pro Export possible, import complex
Bitpanda Pro Export possible, import complex

Closed

No login, no export. Reconstruction via on-chain analysis, archived data and memory protocols.

FTX Insolvent since 2022
Bittrex Closed 2023
Celsius Insolvent since 2022
Cryptopia Hacked/Closed
MT.GOX Insolvent since 2014

Usually Works Well

API connection delivers complete historical data as well. CSV as backup recommended.

Bitpanda
Kraken
Coinbase
Bison
Bitcoin.de
Bitget

Record Retention Requirements

In Austria, § 132 BAO requires a 7-year retention period for tax-relevant documents. In Germany, § 147 AO mandates a 10-year retention period for accounting records. Missing exchange histories can become a problem during a tax audit or information request.

Exchanges in Detail

Binance Tax Report: Exporting All Years Completely

Binance is the most widely used exchange and one of the most challenging for complete historical documentation. The API doesn't cover all Binance products, and historical data is often incomplete. Relying on the API alone leaves gaps.

The Problem with Binance

  • The API doesn't cover all products: Spot, Earn, Staking, Futures and transfers run on different endpoints
  • Historical data via API is often incomplete, especially for older transactions and less-used products
  • CSV exports fill the gaps but must be correctly merged with API data, otherwise duplicates occur

Exporting Wallet History

  • On-chain wallets (Ethereum, Solana, BNB Chain) are accessible via blockchain explorers at any time – no login required
  • Exchange-internal wallets (Binance, Coinbase) are only accessible through account exports
  • Multi-chain wallets require a separate export or API call per chain
Real World Case

8 Exchanges, 1 Tax Tool, 0 Complete Imports

A recent case: 8 exchanges with incomplete or missing imports — despite API connections where available.

5 Exchanges connected via API — with gaps

Binance, Gate.io, Kucoin, Bybit, MEXC

3 Exchanges only importable via CSV

FTX, eToro, OKX: No API available or exchange no longer exists. Import only via CSV exports.

5 API insufficient for 5 exchanges

MEXC, Bybit, Kucoin, Gate.io, Binance: CSV exports needed as supplement, or import entirely via CSV then synchronize with API.

5 Manual import for 5 exchanges

FTX, OKX, Kucoin, MEXC and Gate.io: The client's tax tool was unable to correctly read the raw data. Every exchange has different data formats and transaction types. The raw data had to be manually processed and converted into a readable format.

The biggest challenge: every exchange has its own raw data formats and transaction types. Without experience with these formats, it is nearly impossible to get the data correctly into the tax tool.

TX-Partner Approach

How TX-Partner Reconstructs Your Exchange History

TX-Partner knows the specifics of every exchange: API limits, CSV formats, raw data structures. That saves weeks of research on your own.

1

Inventory

Record all exchanges, wallets and time periods used. Which access still exists? Which exchanges have closed? Where is data missing?

2

Data Acquisition

Set up API connections, pull CSV exports, submit support requests to exchanges. For closed exchanges: use on-chain analysis and archived data.

3

Process Raw Data

Read CSV files, correctly assign transaction types, standardize formats. Every exchange has its own data structures. TX-Partner knows them all.

4

Tax Tool Import

Import cleaned data into Blockpit or CoinTracking. Synchronize API + CSV. Cost basis correct, transfers assigned, no negative balances.

Recommended for you

You might also be interested in

Reconstruct DeFi History
Reconstruct Records Sub-page

Reconstruct DeFi History

LP tokens, yield farming, cross-chain bridges: retroactively document on-chain data.

Learn more
Reconstruct Crypto History
Crypto Documentation 8 min.

Reconstruct Crypto History

Restore missing transaction data step by step.

Read article
CoinTracking Missing Transactions
CoinTracking 6 min.

Fix CoinTracking Missing Transactions

Why transactions are missing and how to fix them.

Read article

Exchange history fully reconstructed

Free assessment of your exchange data as a basis for correct tax reports and complete documentation.

Free Documentation Check
FAQ

Frequently Asked Questions

TX-Partner reconstructs exchange histories going back 7 or more years. Even when an exchange has closed or an account was deleted, on-chain analysis, archived data and support requests can recover a surprising number of transactions.
Most exchanges limit API exports to 12 months. Binance allows a maximum of 15 exports per month. MEXC, Bybit, Kucoin and Gate.io often deliver incomplete data via API. That's why TX-Partner combines API data with CSV exports and manual processing.
Blockpit shows negative balances or "Missing Cost Basis". CoinTracking sets acquisition costs to EUR 0. The result: phantom gains and an inflated tax bill. TX-Partner imports the missing exchange data and corrects the cost basis in your tax tool.
Yes. For closed exchanges like FTX, Bittrex, Cryptopia or Celsius, TX-Partner combines on-chain analysis, archived export data and memory protocols from the client. Based on logical patterns from on-chain research, individual trades can often be reconstructed. The blockchain never forgets, even when the exchange no longer exists.
Back to Reconstruct Crypto Records