CoinLedger supports many exchanges through API, but in some cases exchanges do not export the complete range of transaction history. This guide outlines current limitations with API import for each exchange and recommended steps that you can take to get your full transaction history imported.

These transaction types are not returned by Binance's API:

Further, Binance restricts API imports for US traders. Any Binance user who previously had a working API import from Binance may try to re-sync their API and see a generic error message. It's recommended that you switch to a file import instead.

If you're struggling to access your Binance account as a US trader, there are a few tips to try. One method that has worked for US traders in the past is messaging Binance support and asking them to enable access to your account for a specific window of time. This way, you can export copies of all your trade files from Binance and keep them for your records. Make sure to download the Trade History file which is the version accepted by our software, but you might also want to download other copies of the Transaction History file as well just to have a backup.

Another thing to try is to log in to your account with a VPN. This does not always work, but we have seen that some customers have success with this.

These transaction types are not returned by Binance.US's API:

Bibox's API only returns trades from the past 4 months. To get access to your complete trade history, we recommend switching to a file import.

These transaction types are not returned by BitMart's API:

These transaction types aren't currently supported by CoinLedger, and will cause your import to fail:

Please note BitMart has a date range limit on their API calls which means they only return data from the past 30 days. As a workaround, we recommend importing via our Universal CSV template instead.

These transaction types aren't currently supported by CoinLedger, and will cause your import to fail:

These transaction types aren't currently supported by CoinLedger, and will cause your import to fail:

Additionally, please note that Celsius' API categorizes some fiat buys as transfers/deposits. These can be reclassified in the CoinLedger app.

These transaction types are not returned by CoinSpot's API:

Additionally, CoinSpot's API may not return timestamps for certain trades, which can cause the import to fail. This issue is actively being worked on by the exchange.

These transaction types aren't currently supported by CoinLedger, and will cause your import to fail:

These transaction types aren't currently supported by CoinLedger, and will cause your import to fail:

These transaction types are not returned by KuCoin's API:

These transaction types aren't currently supported by CoinLedger, and will cause your import to fail:

Additionally, U.S. users may not have access to API Keys on KuCoin. New U.S. customers are not able to complete KYC on KuCoin. According to recent KuCoin policy changes, this means U.S. users may not have the ability to create API keys on KuCoin. For this reason, we recommend all U.S. users of KuCoin switch to using a CSV File Import instead.

Furthermore, KuCoin trading account API Keys cannot access data from KuCoin sub-accounts. To import transactions from sub-accounts, log into every sub-account and create a new API Key. The process of creating a new API Key for the sub-account is exactly the same as for the main account, and can be found here.

Finally, due to a limitation within KuCoin's API, transactions before 2/18/2019 may not be imported. If you need to import trades prior to this date, follow this guide to export your KuCoin CSV files prior to 2/18/2019, or send a request for your complete trade history to KuCoin support.