This page explains how to get an API key for Bitstamp's transaction history (Trades/Withdrawals).
Contents
1．Our Support Status for Bitstamp
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
2．Caution
If you establish API connectivity after uploading trade history via trade history files, any trades that happened during the same "minute" as the last trade uploaded via the file may end up as duplicates. For example, if the last trade uploaded via the file has a timestamp of 12:34:00, the API connection would fetch any trades with the timestamp of 12:34:00 onwards.
3．How to get API Key for Bitstamp
1. Click the user icon in the upper right and select "Settings".
2. In the Account Settings page, click "API Access", and then click "New API key".
3. In the "API Access", you do not need to select anything.
4. Enable "User transactions".
5. Click "Enter 2FA & Submit".
4．How to add your Bitstamp 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.