Uploading Transaction History: Switching Between Exchange Files and API – Key Points

This help page explains how to combine exchange files and API integration to reflect transaction history from the same exchange.

1．Switching from Exchange Files to API

1.1 Introduction

Even if you sync API after uploading transaction history via exchange files, the system is designed to import only the transactions from the API that occur after the latest transaction date in the uploaded file. This prevents duplicate entries, ensuring that, in principle, transactions are not recorded twice.

1.2 Important Notes

When switching between exchange files and API integration, there is a rare possibility that transactions near the transition point may be imported twice. After switching to API integration, please review your transaction page to ensure there are no duplicates. If duplicates are found, kindly delete them manually.

Note: Since API integration retrieves transaction timestamps with millisecond precision, duplicates may occur due to the system's design to prevent missing transactions that occur within the same millisecond.

1.3 How to Switch from Exchange Files to API

Please proceed to sync the API while keeping the exchange file uploaded.
How to manage (add/sync) your API keys with exchanges

By default, the connection endpoints uploaded via exchange files are unchecked. If an endpoint you have transactions with is unchecked, please manually select it. Only transactions occurring after the latest transaction date from the uploaded file will be automatically reflected.

Note: You can verify the latest transaction date for each connection destination via "API Integration Screen > API Connections."

Example: Switching from File Upload to API Integration for Bitbank

If you have been reflecting your transaction history through file uploads for Bitbank and wish to switch to API integration, please check the box labeled "Bitbank/Exchange" and click "Submit." This action will import transaction history from the API starting from the latest transaction date already reflected via file upload (e.g., 5/15/2025 23:11:05).

2．Switching from API to Exchange Files

2.1 Introduction

To prevent duplicate entries, the system is designed such that, for the same exchange, transaction history files cannot be uploaded while API key is added to cryptact.

2.2 Important Notes

When uploading an exchange file, you cannot specify the transaction date; therefore, all transactions within the file will be imported.
If you wish to filter by date, please specify the date when downloading the file from the exchange.
If date specification is not possible and the file contains transactions already imported via API, duplicate entries may occur.
In such cases, please manually delete the duplicate records from your transaction list.

2.3 How to Switch from API to Exchange Files

1. Delete the API connection

Due to the risk of duplicate entries, the system is designed such that when API integration is active for the same exchange, transaction history files cannot be uploaded. Therefore, please delete the API integration.

Note: Deleting the API integration will not remove the transaction history records already reflected in your transaction list.

2. Upload the exchange file downloaded from the exchange platform.

When uploading, you cannot specify the transaction date, so all transactions within the file will be imported. If you wish to filter by date, please specify the date when downloading the file.

How to get trade histories from exchanges
How to upload trade history using exchange files

3. Delete duplicate transactions

If you were unable to specify the date when downloading the file in step 2, and the file contains transactions already imported via the API, duplicate entries may occur. In such cases, please delete the duplicate transactions from your transaction list.