This page explains how to get an API key for bitbank's transaction history.
Contents
1．Our Support Status for bitbank
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 bitbank
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.
How to Create a Custom File
2．How to get an API key for Bitbank
1. After login, click the Person icon and select "API"
2.Click "APIキーの発行"(Generate API Key)
3. Select "参照"(Read Only) as the entitlement and click ”確認する” to generate the API key.
*Label is a required field. Please set it to something that is meaningful to you.
4. Make sure the permission is set to “参照” then click “発行する”
5. Click the arrow next to the creation date.
6．Add API connectivity to bitbank by entering the generated API key and secret via Connect to your exchanges.
3．How to add your bitbank 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.