API/CSV issues (public)

Receiving API error when syncing on all my Cardano wallets for the last 5 days. The error is "The API is currently experiencing some issues (). Please try again shortly". This occurred after blockchain update.

Wallet: Coinbase Prime Import type: API I activated a new API key in Coinbase Prime but when trying to sync the wallet I get an error: Access denied, check your API keys When I open the details, I see: Access denied: You do not have permission to perform this request. And no transactions get imported

Some USDT transactions where LP is created are not imported.

There appears to be a change in the way the file is formatted and our mapper needs amendment. The equivalent field is not being imported with Net worth currency must be fiat error. For now, please use a workaround with custom file format accepted by Koinly. https://support.koinly.io/en/articles/9489976-how-to-create-a-custom-csv-file-with-your-data

When I export transactions using the Bulk Edit in Excel feature, I get this error: “A bulk action is already in progress for this portfolio. Please wait for it to complete” This also happens when trying to use the Bulk Edit feature.

The file fails to import with the error. This was reported to the developers. In the meantime, please resort to manual edits to our Simple custom import layout: https://support.koinly.io/en/articles/9489976-how-to-create-a-custom-csv-file-with-your-data

Some wallets are not syncing with this error. Only some transactions get imported leaving a large amount of negative balances. Developers are notified about this error and are investigating.

Some trade operations import an ETH duplicate. This is probably caused by internal/L2 settlement transfers being picked up by our importer. Developers have received a sample dataset and will look into patching this issue. As a workaround - please delete duplicates manually.

Wallets appear to fail syncing. Please resort to manual entry or 3rd party service like Stake.Tax in order to export the CSV files. You can choose Cosmos+ (v1 or V2) for export with base currency CRO. Developers are looking into the issue.

Card_top_up operations in the crypto_transactions_record should be skipped. We currently import it as a plain withdrawal with a USD worth. This operation is actually included in the card_transactions_record but is skipped as a duplicate. In the card_transactions_record file, you can clearly see a trade between crypto>fiat with correct figures. Workarounds: 1) Edit the withdrawals to be trades. or 2) Delete the Withdrawals from crypto file, add the trades from the Card file.