Crypto.com API: Subsequent syncs import duplicate transactions (partial fills)
complete

Jack
When I sync my crypto.com account using my API key/secret, the initial sync is correct but if I sync the wallet again, a lot of balances are wrong. I noticed that additional partial fills (duplicates) are added to already existing trades.
Workaround
I can try setting the "Start import from" date after every sync to stop duplicates from importing, or switch to a CSV import instead of the API.
Activity Feed
Sort by
This post was marked as
complete
This post was marked as
complete
This post was marked as
planned