Fix an exchange sync error

How a sync error shows up

Open Exchanges & wallets. A source that cannot connect shows an Error pill on its card. Below the figures is a short hint: the first sentence of the reason, followed by "Open for details." If Coinfig has no reason stored, the hint reads "Sync failed. Check credentials or retry."

The card has two buttons:

• Update credentials opens a dialog with an API key field and an API secret field. Leave a field blank to keep the value you saved before. Press Save credentials & retry sync, and Coinfig starts a sync straight away.
• Retry runs the sync again with the key you already saved.

Open the card for the full story. It shows Last sync failed with the complete message from the exchange and the time it happened. Below that is an Update API credentials panel, which does the same job as the button on the card.

Why the error appears after you connect

Coinfig does not test a key when you connect it. A wrong key is accepted, and the error appears after the first sync attempt, usually within a minute or two. Check the card shortly after you connect a new source.

Paused syncing and the email

When an exchange rejects the key twice in a row, Coinfig pauses syncing that source. The message starts: "Sync paused after 2 failed attempts in a row because the exchange rejected this API key. Update the key, then press Sync now." Syncing resumes when you save a new key, press Retry on the card, or a sync succeeds.

The first time an exchange rejects a key, Coinfig sends one email. The subject names the source, for example "Action needed: Luno could not connect". You can turn these notifications off.

What it does to your reports

Until the error is fixed, your reports miss everything on that account. If no transactions could be imported at all, report generation tells you the exchange rejected the API key. In its words: "This is a connection problem, not an empty account." Accountants checking a client's file should treat an Error card as missing data, not as an account with nothing in it.

First, rule out a temporary problem

An exchange that is down, in maintenance or limiting requests does not turn the card to Error straight away. Coinfig retries on its own and waits longer between each attempt. The card only shows Error after about 8 failed attempts in a row.

If you suspect the exchange is having trouble, wait. Do not press Sync now over and over. Kraken in particular can lock API access for about 15 minutes.

If the message names the key, the secret or a permission, it is not temporary. Find the matching cause below.

Wrong key or secret

This is the most common cause. The key or secret was pasted with a character missing, the two were swapped, or the key belongs to a different account or sub-account.

The message usually says the exchange rejected the credentials. For example: "VALR rejected the API credentials. Verify the API key + secret in VALR → Account → API Keys and update this source."

Kraken and Bybit say when the signature is the problem. The signature is made with the secret, so a signature error means the secret is wrong or the key and secret are swapped. Kraken's message starts "Kraken rejected the request signature" and goes on to say the API secret is wrong or the key and secret are swapped.

KuCoin also needs the passphrase you set when you created the key. Check it as well.

Fix: copy both values again from the exchange and paste them into Update credentials. Most exchanges show the secret only once, when you create the key. If you no longer have it, create a new read-only key and use that.

Expired or revoked key

The key was deleted on the exchange, or it reached an expiry date.

Examples:

• Luno: "This Luno API key has passed the expiry date set in Luno. Create a new key in Luno → Settings → API Keys, leave "Set expiry date" off, and update this source."
• Luno also tells you when it cannot find the key at all. That means the key may have been deleted or revoked.
• Bybit: "Bybit API key has expired."
• MEXC disables keys that have no IP restriction after 90 days.

Other exchanges do not say why. An expired or deleted key shows as "rejected the API credentials", the same as a wrong key.

Fix: create a new read-only key on the exchange, then save it with Update credentials.

Missing permission

The key is valid, but it is not allowed to read part of your history. This happens when not every read or view box was ticked when the key was created.

The message names the missing permission. Kraken, for example, says: "The key itself is still valid (it has not been revoked), enable the permission in Kraken → Settings → API → (this key) → Permissions, then retry."

What each exchange needs:

• Luno: read access for balances, orders, sends, receives and withdrawals.
• Bybit: read access to "Account Info" and "Asset".
• Bitstamp: "Account balance" and "User transactions", both read.
• KuCoin: the "General" permission, read.
• VALR: follow the steps in the VALR guide.

Fix: on most exchanges you can edit the existing key and add the read permission. You do not need a new key. Then press Retry on the card.

Binance is the exception. It reports a missing permission, an IP restriction and a wrong key with the same error code. Check all three in Binance API Management.

Never tick trade or withdraw permissions. Coinfig only reads your data and never needs them.

Older history is missing, with no error

Some exchanges only return a limited window of history through their API. KuCoin returns about 365 days, Bybit about 730 days and Poloniex about 180 days. Binance sets a different limit for each type of data.

The card shows Synced, so nothing warns you. You find out when older trades, deposits or withdrawals are missing.

Fix: export a CSV from the exchange for the older years and add it to the same source. Binance API sources have a CSV top-up option in the source details. Then check your Data Completeness Score, which flags history that is still missing.

Do not delete and re-add an API source to refresh it. History the exchange no longer returns cannot come back that way, and deleting the source removes what was already imported.

IP restriction on the key

If you restricted the key to certain IP addresses, the exchange refuses Coinfig's requests. Bybit and MEXC say so in the message. Binance reports it with the same code as a wrong key.

Fix: remove the IP restriction from the read-only key you use for Coinfig, then press Retry.

Sub-accounts

One API key covers one account. A key from your main account cannot read a sub-account, and a key from a sub-account cannot read the main account.

Fix: create a key in each sub-account and add each one as its own source.

A key that will not fail

When you create a key, check each of these:

• Read-only. No trade or withdraw permissions.
• No expiry date, or a long one.
• No IP restriction.
• Every read or view box ticked.
• Copy the secret before you close the page.
• One key per account or sub-account.

The exchange guides walk through key creation step by step: Luno, VALR, Kraken, Binance, Bybit and KuCoin. To see the Error state and the fix on screen, watch Fix an exchange sync error.

Still stuck?

Contact support and tell us which source shows the error and the full message from the card. Our support team replies within one business day.