-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: how are duplicate transactions handled? #65
Comments
@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 I've noticed that in the readme, thank you! Still, there might be something useful here, rather than reinventing everything. |
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). |
Neat, thanks again! I've made a note of your project and we'll consider how to proceed best. |
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
The text was updated successfully, but these errors were encountered: