Integration matrix

Blockpit's 21bitcoin CSV importer lists deposits, withdrawals and trades as supported.

Vendor note: "21bitcoin does not offer an API for tax software"

CSV file import of the complete transaction history.

CSV file import only; Koinly says to download the entire transaction history. Vendor note: "You'll need to download your entire transaction history from 21Bitcoin."

Blockpit's Abra page lists Auto-Import and Excel Import but does not say how Auto-Import connects, so only the Excel/CSV template is counted here. Vendor note: "Auto-Import"

CoinLedger says Abra's Transaction History file imports as-is. Vendor note: "Import the file as is. No manual work is required!"

Vendor note: "Abra does not offer an API."

Vendor note: "By simply providing Divly with a wallet address, all your transactions, including the native tokens, will be imported automatically."

Koinly imports Abra's Transaction History CSV via File import. Vendor note: "Upload the files you downloaded from Abra (one at a time) and click on Import"

CSV import only; if the 2018 export is missing, TokenTax says to request it from Abra support. Vendor note: "Abra data is currently supported via CSV import only."

Vendor note: "To import your Abra wallet transactions via CSV, login to the ZenLedger app, go to the Imports tab, select Exchanges, and choose Abra."

Koinly says Acala has shut down and API sync no longer works; its page offers only file import of saved history. Vendor note: "Blockchain Acala has been shut down and API sync is no longer possible."

Blockpit's AdaLite page lists Auto-Import and Excel Import; Blockpit's help says automatic wallet and blockchain imports use your public wallet address. Vendor note: "Auto-Import"

Koinly's 'API' option is pasting each coin's public address; this page gives no CSV upload steps. Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

Blockpit's AirGap page lists Auto-Import and Excel Import; Blockpit's help says automatic wallet and blockchain imports use your public wallet address. Vendor note: "Auto-Import"

Vendor note: "Repeat the previous steps for each blockchain you want to import."

Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

Only Akashnet-2 history from 9 Mar 2021 onwards imports. The article's Transition-to-Manual banner names "DeFi Kingdoms" (vendor copy error), not Akash. Vendor note: "Only transactions from the start (March 9, 2021) of the Akashnet-2 can be imported."

In CoinTracking's import directory (no per-chain page); method per its import guide.

Divly's guide has you generate the CSV from your Algorand address with the third-party Stake Tax tool, then upload it to Divly. Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "you’ll need to add your public address from every wallet you use to interact with Algorand"

Listed as "Algorand" on TokenTax's integrations page. TokenTax's help says chains are imported by entering a wallet address; no Algorand-specific steps are given.

Public address sync; native-bridge deposits and native yield (APE, apeETH, apeUSD) arrive without a transaction and must be added manually.

Listed as "Apechain" on TokenTax's integrations page. TokenTax's help says chains are imported by entering a wallet address; no Apechain-specific steps are given.

Listed as "Aptos" on TokenTax's integrations page. TokenTax's help says chains are imported by entering a wallet address; no Aptos-specific steps are given.

The page is titled Arbitrum One.

In CoinTracking's import directory (no per-chain page); method per its import guide.

Vendor note: "you’ll need to add your public address from every wallet you use to interact with Arbitrum in order for Koinly to calculate your crypto taxes correctly"

Vendor note: "This integration is currently in BETA. Transactions from this API should be reviewed for accuracy once imported". Import is by entering a wallet address.

Some internal EVM transactions (wrapping withdrawals, bridging deposits) may not import automatically; ERC1155 NFT balances are not synced. Vendor note: "Missing transaction data must therefore be added manually."

Only the most recent 10k transactions sync; older ones must be added manually. Vendor note: "Older transactions need to be added manually"

Blockpit's Arculus page lists Auto-Import and Excel Import; Blockpit's help says automatic wallet and blockchain imports use your public wallet address. Vendor note: "Auto-Import"

Koinly's 'API' option is pasting each coin's public address; this page gives no CSV upload steps. Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

Listed as "Arculus" on TokenTax's integrations page. TokenTax's help says wallets are imported by entering a wallet address; no Arculus-specific steps are given.

Blockpit's Argent page lists Auto-Import and Excel Import; Blockpit's help says automatic wallet and blockchain imports use your public wallet address. Vendor note: "Auto-Import"

Vendor note: "However, when there are 3 or more assets in the same transaction, Divly will import them as deposits and withdrawals."

Koinly's 'API' option is pasting each coin's public address; this page gives no CSV upload steps. Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

Public address sync; add the address of every wallet you used with ARK. CSV upload is mentioned only in the intro, with no steps, so CSV is not counted.

Paste your public ARK address into ZenLedger's address field and pick the blockchain from the dropdown.

Blockpit discontinued its automated AscendEX integration when the exchange ceased operations and API services on 1 Jul 2026; new transactions go in via its CSV template or manually. Futures PnL and Earn rewards were not supported.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "Note that AscendEx only allows for data export from their API for the past 3 months."

Koinly says AscendEX ceased operations on 1 Jul 2026 and data can no longer be exported from it, so only CSV files you saved earlier can be imported. Vendor note: "You will not be able to export any data from it."

ZenLedger's page describes import methods only in general terms across exchanges, not an AscendEX-specific method. Vendor note: "Select the exchange that you are looking to import, and instructions will be provided for that specific exchange!"

Public address sync; the explorer misses some transactions, mostly rewards and balances claimed from dApp contracts. Vendor note: "Some transactions may be missing, since the block explorer does not index all transactions."

Blockpit's Atomic Wallet page lists Auto-Import and Excel Import; Blockpit's help says automatic wallet and blockchain imports use your public wallet address. Vendor note: "Auto-Import"

Vendor note: "CSV files exported from Atomic Wallet do not contain information about which coins/tokens have been transferred."

In CoinTracking's import directory (no per-wallet page); method not stated.

CSV export is per coin; repeat for each one. Vendor note: "Don't change the file name when using Divly as we use it to figure out what cryptocurrency the transactions represent in the file."

Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

Vendor note: "Certain internal transactions on EVM chains (e.g., withdrawal transactions related to wrapping; deposit transactions related to bridging) can currently not be imported automatically in all cases."

In CoinTracking's import directory (no per-chain page); method per its import guide.

Divly's integration uses your public Avalanche address.

Koinly's guide covers Avalanche C-Chain. Vendor note: "This integration can support wallets with up to 50k transactions"

The guide covers the Avalanche C-Chain.

TokenTax's guide imports Avalanche C-Chain by wallet address; its X-Chain import is in beta and P-Chain needs its manual CSV template.

Blockpit's Backpack Wallet page lists Auto-Import and Excel Import; Blockpit's help says automatic wallet and blockchain imports use your public wallet address. Vendor note: "Auto-Import"

Koinly's 'API' option is pasting each coin's public address; this page gives no CSV upload steps. Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

In CoinTracking's import directory (no per-chain page); method per its import guide.

Listed as "Base" on TokenTax's integrations page. TokenTax's help says chains are imported by entering a wallet address; no Base-specific steps are given.

In CoinTracking's import directory (no per-chain page); method per its import guide.

Listed as "Berachain" on TokenTax's integrations page. TokenTax's help says chains are imported by entering a wallet address; no Berachain-specific steps are given.

Blockpit's Best Wallet page lists Auto-Import and Excel Import; Blockpit's help says automatic wallet and blockchain imports use your public wallet address. Vendor note: "Auto-Import"

Koinly's 'API' option is pasting each coin's public address; this page gives no CSV upload steps. Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

CoinLedger says Bibox's Transaction History file imports as-is. Vendor note: "Import the file as is. No manual work is required!"

Vendor note: "Note that Bibox only allows for data export for the past 4 months from their API."

Vendor note: "Bibox does not offer an API for tax software"

Divly imports Bibox's XLSX export by file upload; it has no Bibox API connection. Vendor note: "You can import Bibox transactions into Divly by downloading and importing a XLSX file."

Koinly takes Bibox's Access Key and Secret Key, or CSV files exported from Bibox order history (Koinly's CSV tab; you may need several files). Vendor note: "Follow these steps to sync your Bibox data automatically to Koinly:"

Bibox exports start in late 2019; for older trades TokenTax says to ask Bibox support for a full CSV. Vendor note: "Bibox data is supported via either API or CSV import."

ZenLedger's how-to is by Bibox receiving address. Vendor note: "Paste the receiving address you copied from Bibox into the wallet address field in ZenLedger."

Add each blockchain's address separately. Vendor note: "Repeat the previous steps for each blockchain you want to import."

Koinly's 'API' option is pasting each coin's public address; this page gives no CSV upload steps. Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

Blockpit's BigONE page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "connect with Koinly via API or by uploading a CSV file of your transaction history"

ZenLedger's how-to is by BigONE receiving address. Vendor note: "Paste the receiving address you copied from BigONE into the wallet address field in ZenLedger."

Coinpanda's Bilaxy page says the API is offline, so upload CSV history you saved earlier. Vendor note: "Bilaxy suffered a hot wallet hack on August 28, 2021. The API is currently offline due to this, but you can still upload old CSV files."

Vendor note: "Spot Market Trades older than 720 days (2 years) are not available via API."

Vendor note: "A CSV covers spot trades only. Card and bank purchases, and staking or mining rewards, need the API import or manual entry."

Vendor note: "Internal Binance transfers between your Spot, Futures, and Margin wallets can only be imported from the past 6 months."

Vendor note: "Earn transaction history and wallet balances is not supported. Auto invest transaction history is not supported."

Vendor note: "The Binance API is not sufficient for tax reporting in most cases and is therefore not supported for tax imports."

Vendor note: "Missing data (not provided by Binance via API at all): Bot trades and NFT trades"

TokenTax's help article says new API connections are not currently possible; new/missing data via CSV. Vendor note: "Due to changes on Binance's end, new API connections are not currently possible (especially for U.S.-based users)."

Blockpit discontinued its automated Binance US integration in October 2026; existing integrations keep their data and new transactions go in via its Excel template or manually. Staking rewards were not supported.

The API cannot import card or ACH fiat purchases; use the file upload for those, and upload the CSV without opening or editing it.

Fiat purchases and Boost-event rewards are not provided by the Binance.US API and must be added manually.

Spot transactions, per TokenTax's guide.

CSV/Excel only (no API). The current v3 format (two files) does not cover Wealth (Earn, Loan, Dual Invest), RewardsHub, LaunchHub or fiat deposits/withdrawals.

Spot trades import; futures and copy-trading results are added with CoinLedger's Margin Gain transaction type. BingX limits export ranges, so several files may be needed.

Vendor note: "Futures transactions cannot be imported from the API at this point."

Vendor note: "Fiat-to-crypto conversions and bank card crypto purchases are not included in the BingX export"

API gives futures for the last 3 months only (max 1,000 trades) and no copy trading, Earn, conversions or Wealth; use CSV for those. Vendor note: "BingX's API has multiple limitations and may not provide all your data"

CSV only, from Bison's Transaction History (CSV) report under Account, Reports (help article dated 16 Sep 2026). Vendor note: "download your complete transaction history as a CSV file"

Vendor note: "BISON does not support API connection at the moment."

Vendor note: "Bison does not offer an API for tax software"

CSV only; download a fresh file to include new transactions. Vendor note: "Make sure to download the CSV files every time you want to include the latest transactions."

CSV only; Bison emails the Transaction History CSV, which you then upload. Vendor note: "Once received, download the attached CSV and import it to Koinly"

Blockpit's Bit2Me page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "Bit2Me does not support API connection at the moment."

CSV only; export each year from Bit2Me and upload every file. Vendor note: "You'll need your entire trading history from Bit2Me so you may need to do this multiple times and upload all of these files to Koinly."

Blockpit's Bitazza page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Blockpit's bitbank page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "The Bitbank API does not currently provide access to deposits and withdrawal history."

Divly's bitbank guide is in Japanese. bitbank exports at most 500 rows per file, so active traders need several files; upload deposit and withdrawal histories too.

API only (bare CSV tab not counted). Vendor note: "API is in beta so may not be fully functional"

Blockpit's Bitbns page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

Koinly's Bitbns page says Bitbns has shut down and data can no longer be exported from it, so rely on CSV files you saved earlier. Vendor note: "You will not be able to export any data from it."

Public key (address) per blockchain; BTC, BCH, LTC and DOGE via xpub. Blockchains without an automatic import need a manual integration. Vendor note: "you have to import this transaction data manually into a Manual Integration."

In CoinTracking's import directory (no per-wallet page); method not stated.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "Note that beta integrations might not always sync properly."

CSV file import: Koinly-format yearly statements for activity after May 2024 and a legacy CSV for earlier years (API is only named in an FAQ without steps, so not counted).

Blockpit's general blockchain-integration guide adds Bitcoin by public wallet address or extended public key (xpub, ypub or zpub).

In CoinTracking's import directory (no per-chain page); method per its import guide.

Vendor note: "Some transactions that happened before June 1st 2022 may have the wrong timestamp (off by 1 hour) and need to be edited manually"

Listed as "Bitcoin" on TokenTax's integrations page. TokenTax's help says chains are imported by entering a wallet address; no Bitcoin-specific steps are given.

Blockpit's wallet-integration guide says Bitcoin Cash may need an extended public key (xpub-style account address) rather than a single address.

In CoinTracking's import directory (no per-chain page); method per its import guide.

Vendor note: "We recommend syncing your XPUB key rather than individual addresses."

Listed as "Bitcoin Cash" on TokenTax's integrations page. TokenTax's help says chains are imported by entering a wallet address; no Bitcoin Cash-specific steps are given.

Koinly's 'API' option is pasting each coin's public address; this page gives no CSV upload steps. Vendor note: "Copy the public address for every coin that you have on it (even the ones with a zero balance)"

Blockpit's Bitcoin.de guide prefers the API, with a CSV upload of the full transaction history as well. Vendor note: "Bitcoin.de does not provide trades for the delisted asset BSV via API."

Vendor note: "Bitcoin.de does not provide a complete record of all transactions"

Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Blockpit's guide covers API key import and lists Funding (Lending & Borrowing), OTC/P2P Trades and Securities Trades as not supported.

Vendor note: "Transactions from the last 6 years only can be imported from the Bitfinex API. Older transactions must be added manually."

Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "If you have margin trades, you will need to connect an API to supply all necessary data."

ZenLedger's guide says it supports this platform but only describes import methods in general terms, not for this platform.

Blockpit's help article says the automatic import has ended; new transactions only via Blockpit's Excel template (CSV) or manual entry. Vendor note: "Automated bitFlyer integration has been discontinued as of Oktober 2026."

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Blockpit's BitForex page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

Coinpanda's BitForex page says trading is suspended, so upload CSV history you saved earlier. Vendor note: "After a 2024 service interruption, the platform has kept trading and deposits suspended while processing withdrawals for eligible users."

Vendor note: "If you have transactions on BitForex before 30/10/2020, these will not be included in your CSV file."

Vendor note: "Transactions older than 2 years are not available via API."

Vendor note: "Bitget exports up to 24 months of history, so generate multiple files to cover your full history"

Vendor note: "This integration is currently under construction. We recommend you add your account now and CoinTracker will automatically import your account balances and transactions once this integration is supported."

Vendor note: "Bitget's API only provides transactions for the last 2 years"

Listed as "Bitget" on TokenTax's integrations page. TokenTax's help says CSV upload works for all exchanges; it gives no Bitget-specific steps and does not say whether Bitget has an API sync.

Public wallet address import, one blockchain at a time.

Public address import only (the CSV tab has no steps); Koinly says to copy the public address for every coin, even ones with a zero balance.

Blockpit's Bithumb page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "Note that Bithumb only allows for data export from their API for the past 30 days."

Bithumb CSV downloads are limited to a maximum of 6 months per file, so you may need several files for a full history. Vendor note: "Pick a time frame"

CSV import only. Vendor note: "Bithumb data is currently supported via CSV import only."

Blockpit's Bitkub page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

Vendor note: "While Koinly supports both, please don't mix them and only import one or the other, never both."

Blockpit discontinued its automated BitMart integration when the exchange ceased operations and API services on 26 Aug 2026; existing integrations keep their data and new transactions go in via its CSV template or manually. Futures PnL and Earn rewards were not supported.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "The BitMart API can only provide trade history from the past 2-3 months."

CSV of your full BitMart transaction history; re-download it to include the latest transactions. Divly's guide does not mention BitMart's suspension.

Koinly says BitMart has shut down and data can no longer be exported from it, so the API no longer works and only CSV files you saved earlier can be imported. Vendor note: "You will not be able to export any data from it."

Listed as "BitMart" on TokenTax's integrations page. TokenTax's help says CSV upload works for all exchanges; it gives no BitMart-specific steps and does not say whether BitMart has an API sync.

Blockpit discontinued its automated BitMEX integration when BitMEX ceased operations and API services on 23 Sep 2026; existing integrations keep their data and new transactions go in via its CSV template or manually.

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

API only; Divly says BitMEX's CSV export lacks the data quality it needs. Divly's guide does not mention BitMEX's closure. Vendor note: "Divly now only supports the API from BitMEX."

Koinly says BitMEX closed on 23 Sep 2026 and API sync is no longer supported, so import CSV files you saved earlier. Vendor note: "BitMEX closed its exchange on 23 September 2026, and API sync is no longer supported."

Use BitMEX wallet history (not trade history) for CSV; margin and derivatives need a supporting plan or the Margin Add-On. TokenTax's article does not mention BitMEX's closure.

ZenLedger's guide says it supports BitMEX but only describes import methods in general terms across exchanges, not a BitMEX-specific method. Vendor note: "Select the exchange that you are looking to import, and instructions will be provided for that specific exchange!"

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

CSV file import only; Koinly says to export all years and check the file holds all deposits, withdrawals and trades. Vendor note: "Manually check that the file contains all your deposits, withdrawals and trades"

Blockpit's BitoPro page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Blockpit's guide covers OAuth connection, API key, and a CSV upload. Vendor note: "The alternative Bitpanda CSV upload only includes crypto transactions, lacks sub-wallet structures, and is therefore incompatible with OAuth/API."

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named.

Vendor note: "Make sure to download the CSV file every time you want to include the latest transactions."

Vendor note: "Bitpanda's API does not provide: Staking rewards - rewards need to be added manually"

CSV export needs the BitPay desktop app. Vendor note: "(The mobile app does not currently support exporting.)"

Divly's guide (page title 'How to do your Bitpay taxes in 2022', URL slug Copay) covers the Bitpay Wallet: automatic import from a public wallet address, or a CSV file from the Bitpay app.

Export from the BitPay desktop app, one file per wallet. Vendor note: "Upload the files you downloaded from"

TokenTax says new BitPay API connections are not possible; its CSV steps export spot history from the BitPay Card tab. Vendor note: "Due to changes on Bitpay's end, new API connections are not currently possible."

Blockpit's Bitrue page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

Vendor note: "Rewards from the Earn program are not available from the API."

Vendor note: "Bitrue does not offer an API for tax software."

Bitrue needs three CSV files (deposits, withdrawals, trades), and more than one file per type if your history is longer than a year.

API misses futures, BTR dust conversions, Earn interest/rewards and loans; Koinly says to add those manually or with CSV files.

CSV only (no API); Bitrue exports up to 3 months per file. Margin, futures and derivatives need a supporting plan or the Margin Add-On.

Blockpit's Bitso page lists only Excel Import (upload via Blockpit's Excel/CSV template); no automatic API import is shown. Vendor note: "Excel Import"

CoinLedger's only stated method is mapping your export into CoinLedger's own CSV format; no dedicated importer is named. Vendor note: "Import your transaction history directly into CoinLedger by mapping the data into the preferred CSV file format."

Vendor note: "Currency conversions are not provided by the Bitso API. These trades will need to be added manually until Bitso addresses the issue"