This page explains how to get an API key for Binance Japan's transaction history.
Contents
1．Our Support Status for Binance Japan
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 Binance Japan
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 Binance Japan
Please select "English (Japan)" to access to Binance Japan's English site.
1．Log in to Binance Japan, click on "Account".
2．Select ”API Management” and click on ”Create API”.
３．Select"System generated"and click on"Next".
４．Name your API Key.
5．You will need your 2 FA code
6．Click on "Edit restrictions "in right top.
7. Then, make sure to check "Unrestricted (Less Secure) before save the edit.
8．You will need your 2 FA code
9．The API Key is created. Save your API Key and Private Key.
*Make sure to take note of the Secret Key displayed at the time of creation. If you miss this opportunity, it will be obscured with asterisks and cannot be retrieved for confirmation. You would need to create a new one in that case.
3．How to add your Binance Japan 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:
Ensure that the desired transaction types are selected.
(Note: If transaction history has been previously uploaded via file, the checkboxes are set to off by default. Please adjust accordingly.)
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.