This page introduces how to obtain an API key for Kraken's trading history.
Contents
1．Our Support Status for Kraken
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.
Custom File for any other trades
1-2．Time period that can be retrieved
-
Only transaction history from the past 120 days can be retrieved.
Due to exchange limitations, only the past 120 days of transaction history can be automatically retrieved. To include older transactions, please upload a file obtained from the exchange or create and upload a Custom File.
How to get trade history from AscendEx
-
Please re-sync the API manually at least once every 120 days
Transaction history older than 120 days will not be reflected, so it is necessary to perform regular API re-synchronization within that period after linking.
2．How to get API Key for Kraken
1．Click on the profile icon on the top right hand corner, then click on Security
2．Click on "Create API key" in API tab.
3．Click on Go to Kraken Pro.
4．Click on Create API Key
5．Name your API Key and select the settings you need. Then click on Generate key
6．You will need your 2 FA code
7．The API Key is created. Save your API Key and Private Key
3．How to add your Kraken 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.