My Exchange Is Failing To Sync

API connected exchanges are great, though occasionally you may see indications in your account that an API sync has failed. While it can be frustrating, there are a few simple steps we can take to get that API up and running. 

Please note: If you see the message "Currently Syncing" when you try to connect your exchange, this means that the API integration is actively working to bring over your transaction history. This can take some time, so please be patient!

In this article:

• How do I know If my API isn't syncing? 
• What do I do when I notice a failed API connection? 
• Common causes of failed API connections

How do I know if my API isn't syncing? 

To check whether or not your API or wallet connection is still synced, you can go to 'Add Transactions' > Select the exchange or wallet you want to check > Look at the status message directly above the 'Sync Exchange' button.

In that message, you'll see whether the last sync succeeded or failed, and the date and time the last sync was attempted. If your status message says 'Last Sync Failed on {date and time},” then your exchange is failing to sync.

What do I do when I notice A failed API connection? 

Once you’ve confirmed a failed API connection, the first thing  to do is to remove the API connection from TaxBit, and remove any API keys you set up on the platform. To do this, navigate to 'Add Transactions' > Select the exchange or wallet you want to remove > Select 'Remove Exchange' in the bottom left corner.

Next, pull up the matching API set up guide for the platform you're having issues with.These guides will walk you step-by-step through correctly setting up a successful API connection. 

While setting up that connection, always follow the API set up guide when available to avoid some of these common mistakes:

• Entering the wrong credentials into the API set up fields. For example, entering your private key in the field labeled API key on TaxBit, and entering your API key into the field labeled private key. 
• Giving the API key permissions beyond 'read only'. The terminology on a particular platform may be different, but generally speaking we don't want to be able to make any changes to the account you're trying to connect using that API key. 

Common causes of failed API connections

In general, there are two reasons an API connection has failed: 

1. Authentication errors: Either the API you set up has expired, has been removed, or has been disabled by the platform. While this is not something TaxBit can fix, you can generally resolve this issue by setting up a new API key and connecting that new key to your account.
2. Non-authentication errors: There are a multitude of potential causes, but generally it means we need our development team to look into the issue to determine if it's something we can fix on our end, or if the issue can only be fixed by the exchange.  

For non-authentication errors, please be patient while we work with our dev team on this. We are continually working on release fixes to our API integrations to ensure the best possible experience for you.  However, there may be delays as we often rely on the exchange to make the necessary changes for fixing the API connection.  

If you need to import data into your account before we are able to release a fix, reach out to the support team for the best way to bring that missing data into your account without the API integration. 

Still have questions? Send us an email at support@taxbit.com or chat with us using our live chat feature, and we'd be happy to help!