This page introduces how to obtain the API key for transaction history of HashKey.
We apologize for the inconvenience, but we only have a test account for HashKey, so your screen may differ. If you can create a HashKey API, please contact support. If you send us a screenshot of your screen, we will update this help page.
Contents
1．Our Support Status for HashKey
1-1．Types of transactions that can be retrieved
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.
How to Create a Custom File
1-2．Time period that can be retrieved
Due to exchange specifications, HashKey history can only be retrieved within the past month; please click "Sync" in the cryptact HashKey API integration every month to get the latest history.
2. How to Get API Key for HashKey
1. After completing identity verification, click on the profile icon at the top right of the page and click "API Management". Then click "Create API".
2. Set the "API Note Name" yourself and set "API Permissions" to "Read-Only Permission".
3. Enter the following IP addresses in "IP Access Restriction".
52.69.115.51,52.193.138.38,18.179.74.94
4. Click "Confirm" to create the API key. Please keep the API key and secret key safe.
3．How to add your HasKey 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
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.