Skip to main content
CoinSpot - API Import Guide

How to automatically import your CoinSpot transactions into CoinLedger

Lucas Wyland avatar
Written by Lucas Wyland
Updated over a week ago

CoinLedger only needs "Read" or "View" access to import your trade history. This permission protects your accounts. Learn more about API access in this article here.

Jump ahead with this table of contents:

API Import Walkthrough

Step 1:

Log in to your CoinSpot account

Step 2:

  • Navigate to the API section

  • Click on the My Account icon in the top right corner and select API

Step 3:

Click on Generate New API Key

  • Select a name (this can be any name you'd like) for the API key, make sure Read Only is selected for API Key Type and enter your 2FA code

  • Click Create API Key

Step 4:

Click on the confirmation link received by e-mail. You should receive an e-mail from CoinSpot asking to confirm the new API key creation, click on the received link to proceed.

Step 5:

Copy the secret into a safe place. Click View Secret (One Time Only) and copy the secret into a safe place, as you will not be able to recover it later.

Step 6:

Navigate to Step 1. Import. Select Add Account then choose the CoinSpot tab on CoinLedger. Click on Auto-Import then enter your API Key and API Secret into the correct fields. Click Sync Transactions.

When importing your transaction history via API, you will have the option to specify a start date for your import. This feature is designed to prevent duplicate data from being imported. You can access this feature by hitting the Import Settings drop down menu, as shown below, and then specifying a date for your import to start from. All transactions after this date will be imported. You should not do this if you are importing all of your transactions into CoinLedger for the first time.

CoinSpot API Limitations:

These transaction types are not returned by CoinSpot's API:

Additionally, CoinSpot's API may not return timestamps for certain trades, which can cause the import to fail. This issue is actively being worked on by the exchange.
โ€‹

Did this answer your question?