This help page introduces how to add additional API endpoints.
It also provides an overview of how to check and resolve cases where transactions are not reflected, despite the API integration being completed, in situations like the one described below.
- Even though the API key has been integrated, some transaction types are not being reflected...
- In exchanges where the API has been integrated, a new transaction type has been added to cryptact, and you'd like to add it!
Ex: Even though the bitbank API is integrated, the "Transaction History" is not being reflected.
How to check
Solution
If the API synchronization is complete but the history is not reflected
Please check the "Updates of automation" for the relevant exchange.
*If the exchange is not listed in the "Automatic Transaction History Sync Status," please refer to the cautionary notes at the beginning of the "Exchange API Connection" section.
If the transaction types are unsupported or if the transactions are from a period that cannot be retrieved due to the exchange's specifications, the corresponding transaction history will not be automatically reflected.
In such cases, it may be possible to obtain the transaction history by downloading a file from the exchange. Please check the "How to get trade histories from exchanges" to verify if the transaction can be retrieved. If it can be, please upload the file.
If the transaction is unsupported by both the API and file, you will need to manually upload it as custom trades