pynYNAB icon indicating copy to clipboard operation
pynYNAB copied to clipboard

Question: how are duplicate transactions handled?

Open torbengb opened this issue 6 years ago • 4 comments

Hello Matthieu! I love this idea and your solution. I am wondering what happens if you push the same transaction twice, or if you push a transaction that already exists? Does YNAB kill the pushed duplicate, or would you have to handle this yourself?

I'm working on a related project bank2ynab and we are thinking about using the YNAB API. Instead of starting from scratch, perhaps it would be smarter to integrate your solution.

Regards from Austria! -Ben

torbengb avatar Mar 01 '18 11:03 torbengb

@torbengb it's worth noting, this is not the official API. This library uses a reverse engineered version of the API that the web app uses.

scottrobertson avatar Mar 01 '18 11:03 scottrobertson

@scottrobertson I've noticed that in the readme, thank you! Still, there might be something useful here, rather than reinventing everything.

torbengb avatar Mar 01 '18 11:03 torbengb

You will be best waiting for the official API to come out of beta, as this tends to be pretty unreliable (not a fault of @rienafairefr, it's just the nature of how it's built).

This is the reason i migrated away from it for https://github.com/scottrobertson/fintech-to-ynab

If you don't want to reinvent the wheel, adding CSV support for lots of different formats to Fintech to YNAB would be a piece of cake (like 20 lines of code per CSV format).

scottrobertson avatar Mar 01 '18 11:03 scottrobertson

Neat, thanks again! I've made a note of your project and we'll consider how to proceed best.

torbengb avatar Mar 01 '18 11:03 torbengb