A5Getting started1 min 18 sec

Fix an exchange sync error

Why an exchange refuses your API key, and how to get it syncing again.

Fix an exchange sync error: Why an exchange refuses your API key, and how to get it syncing again.

Key points

  • Coinfig does not test a key when you connect it, so a wrong key shows up as Error after the first sync.
  • The card shows the first line of the exchange's message; open it for the full text and the time.
  • A wrong, expired or deleted key needs a new read-only key, saved with Update credentials.
  • A missing permission can be added to the same key on the exchange; then choose Retry.
  • Some exchanges only return recent years through the API, with no error; fill older years with a CSV.
  • Until a source is fixed, reports miss that whole account, and Coinfig emails once when a key is refused.

Chapters

Keep learning

Read the transcript

Your exchange source says Error. It's usually the API key, and it takes a minute to fix.

Error means the exchange refused Coinfig's request. The card shows the first line of why. Open it for the full message. Here VALR rejected the key: it was pasted wrong, or the key and secret were swapped. Luno can't find this key at all. It was deleted or revoked on the exchange, so only a new key will work. If a permission box wasn't ticked, the message names it. Tick it on the same key on the exchange, then choose Retry.

For a wrong, expired or deleted key, choose Update credentials, paste a new read-only key and save. Save credentials and retry sync stores the new key and syncs again straight away.

Some exchanges only return recent years through the API. Fill the older years with that exchange's CSV. Until a source is fixed, your reports miss that whole account. Coinfig emails you the first time a key is refused.

Read the first line. Fix the key, or its permissions. Fill older years with a CSV.