This page explains how to get an API key for Bitrue's transaction history.
Contents
1．Our Support Status for Bitrue
You can check the support status of API endpoints for exchanges on the ”Supported Exchanges & Blockchains” page.
If an exchange provides transaction history via API, we will automatically reflect that data. However, if the exchange does not supply certain information through API or if the provided files lack transaction details or are unclear, those transactions cannot be automatically imported. In such cases, please upload the transaction history manually using a custom file.
Custom File for any other trades
2．How to get API Key for Bitrue
1. Log into Bitrue, click on"API".
2. Click on "Get API key" button.
3. Click on "Create API key" button.
4. Set the API name to whatever you like, then click "Create API key".
5. If you have set up your account to use two-step verification, complete the two-step verification.
6. Go to the email account associated with your Bitrue account, and click the URL. Copy the API Key and the Secret Key.
- All Service: select "Read-Only"
- IP access restrictions: select "Not limited to any IP (low security level) "
- Click "Save settings"
and click "Save settings".
* Secret Key is displayed only once upon creation. Please copy it and keep it somewhere safe. If you miss this opportunity, it will be displayed as asterisks and you will have to create another API key.
3．How to add your Bitrue API key to cryptact
Please select your exchange on the designated screen, enter your API key and secret key, then click "Submit" to initiate automatic API synchronization. If you conduct new transactions later, you'll need to manually click the "Sync" button to update your transaction history.
How to manage (add/sync) your API keys with exchanges
*If you have multiple accounts, you can optionally enter a Sub-account name to reflect each account's history. However, using different sub-account names with the same API key may cause duplicate entries, so please be careful.
Accidental Double Counting in API Integration - Causes and Countermeasures:
Disclaimer
Please note that we will not be held responsible for any damages caused by unauthorized use or other accidents due to API connections. When connecting, please be sure to use the API key specified by us.