This page explains how to get an API key for Bitget's transaction history.
Contents
1．Our Support Status for Bitget
You can check the support status of API endpoints for exchanges on the ”Supported Exchanges & Blockchains” page.
Please refer to the following help page for detailed information on the types of transactions supported.
Our Support Status for Bitget
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 Bitget
１．After logging in, click on the Person icon and select "API keys".
２．Click on "Create API key".
３．Select"System-generated API key".
４．Select the following in Create new API key
- Write a "Note" of some kind.
- Set a passphrase (API token) *This is required for API integration. Please make sure to keep it.
- Select "Read Only" in Permissions.
- Check "Name" in Permission type.
- Check all of the following.
- Set the following for the IP address link *Please note that entering spaces may result in an error 52.69.115.51,52.193.138.38,18.179.74.94
５．Enter security verification
６．API key and secret key creation is complete *Make sure to keep them.
3．How to add your Bitget 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.