This page explains Sync-n-Forget (API connection).
Table of contents
About Sync-n-Forget (API connection)
Sync-n-Forget automatically fetches and stores your transaction history in the background, even for exchanges whose API — due to the exchange's own specifications — limits how far back it can reach. Even if you haven't logged in for a while, it prevents your transaction history from being lost to retrieval deadlines. Connect your API once, and just sync and forget — no need to worry about timing.
What this feature does
Some exchange APIs impose a retrieval deadline — for example, only the most recent few months of transaction history can be retrieved.
Major exchanges: Automatic support status for transaction history
Other exchanges: How to obtain each exchange's API
Until now, if you used such a time-limited API, you had to log in to cryptact and re-sync the API regularly before the deadline passed. If you forgot to re-sync, transaction history beyond the deadline could become impossible to retrieve.
With Sync-n-Forget:
- cryptact automatically fetches and stores your transaction history in the background.
- You no longer need to log in periodically, or log in just to re-sync.
- It prevents transaction history from being lost because you forgot to log in.
Even if you haven't logged in to cryptact for a while, simply log in and sync next time, and the transaction history accumulated in the background can be reflected through a manual sync. (Note: you still need to run the sync yourself, as before.)
How it works
Once you set up the API connection, cryptact collects and stores your transaction history in the background. When you run a sync, the collected history is reflected as transaction history in your account.
How to re-sync (update) the API
Example: how Sync-n-Forget works
As an example, consider an exchange whose API has a retrieval deadline of "the past 3 months." This retrieval deadline (3 months) itself does not change when you use this feature.
January 1: Initial sync
- When you connect the API, the past 3 months (October–December of the previous year) of transaction history is reflected at this point.
- From then on, cryptact keeps collecting your transaction history automatically in the background.
Previously (without this feature)
- Unless you logged in and re-synced every 3 months, history beyond the retrieval deadline could not be retrieved, and gaps could appear in your history.
July 1: You log in and sync for the first time in 6 months
- The API's retrieval deadline is "the past 3 months," but because cryptact has kept collecting in the background, the history from the last reflected date (January 1) up to now (July 1) — that is, January through June — is reflected in full.
- Even though you didn't log in for 6 months, no gaps appear in your history.
If you delete the API connection
- Even if you delete the API connection, the transaction history that was collected in the background while that API connection was being synced is retained behind the scenes.
- So even after you delete the history from your transaction list and delete the API connection, if you add and sync the API again using the same sub-account name, the already-collected transaction history will be reflected again. (The API key itself can be a different, newly regenerated key — only the sub-account name needs to match.)
Eligible plans
This feature is available on Basic and higher paid plans.
Note (about the Data Retention plan)
The Data Retention plan is not covered by this feature. For example, if you move from a paid plan to the Data Retention plan (and during that period trade on an exchange with a time-limited API, such as a 3-month retrieval window), and then return to a paid plan a year later, the transaction history generated during your Data Retention plan period may be lost, as it can no longer be retrieved once the API deadline has passed. If you trade on an exchange with a time-limited API, we recommend keeping a paid plan.
How to use
- Obtain an API key on the exchange you use (an exchange with a time-limited API) and connect it to cryptact. For the API connection steps for each exchange, please refer to each exchange's API connection help page.
- From then on, you do not need to log in and sync periodically to beat the deadline.
- Log in to cryptact and press the Sync button whenever you like. The transaction history that cryptact has been collecting in the background via the API will then be reflected in your account. For detailed steps, see How to re-sync (update) the API.
If a sync error is shown
While a sync error is shown, transaction history cannot be collected in the background during that time either, so please resolve the error.
Errors you need to resolve yourself (invalid API key, expired API key, insufficient permissions, IP restriction, etc.)
- Please check and fix the setting on the exchange side.
- Some exchanges set an expiry on API keys. Please check your exchange account for details.
- If the error shown is "Invalid API key," it is likely that the API key was not obtained using the method described in the help pages, so please first check How to obtain each exchange's API.
Errors handled by cryptact (general errors, unsupported transactions, etc.)
- cryptact is automatically alerted and works on these, so you do not need to contact support or wait.