Scott Robertson Hmmm ... yes, that doesn't work well for the way you have things set up. I'm wondering about (and I'm hesitant to even ask in case it's a dumb question - so apologies in advance) the reasoning behind pulling in transactions by both methods? Is it possible one method will miss transactions? 

This is something they're still discussing internally, so we may be able to find a solution that will work for your setup eventually. 

Pedro Lauro You can use the import_id field when posting transactions (check out the Model tab) to specify whether a transaction brought in through the API should be treated as imported or manually entered. 

If you specify an import_id other than null, you would be able to match transactions brought in through the API to your manually entered transactions :) 

I hope that helps!

Angela We're already using the import_id field, with the id transaction value provided by the bank's API. YNAB does enable the `match` option so I can do it manually. But what I was looking for was the automatic apply of matching rules, just like when I manually import an OFX file. Here's an example:

First image: before import 

Second image: after import (using `/budgets/{budget_id}/transactions/bulk` API)

Kevin K. You should still be able to select a manually entered transaction and one imported through API (import_id specified) and manually match them using that option from the Edit menu when both are selected.  The ability to automatically match when importing through the API is still on our request list. 

Brady Thanks for the reply! That works. Auto-matching via API will be great.

Brady I would also very welcome auto-matching for API-imported transactions.

Brady  Adding my vote for Auto-matching transactions via the API. It would be super useful

Brady   +1 vote

Brady I'm glad I did a search on the forums before making a fresh topic.  Could the API documentation be updated to include the +/-10 day window for matching transactions in the same account?

I built myself a Logic App in Azure to receive webhooks and send on to the YNAB API and the matching of transactions, because I am a creature of habit and buy the same meal every day, was starting to perplex me.

Regardless, love the API and love YNAB for the changes it's made to my life and thought processes.

mydran Thanks for the kind feedback!  Also, your Azure app sounds pretty cool and handy!  I can definitely improve the documentation in this area.  I will work on improving the description for the "import_id" field to explain a bit better how matching works and to note the +/-10 day window for matching.

mydran How are you doing the webhooks?

CNorris The bank in this instance, Monzo, allows a bit of developer access and you can register a webhook to send transactions to.

I used a quick online tutorial to create a webhook as a Web Logic App in Microsoft Azure and adapted it to send to the YNAB API.

mydran Thanks for the update. I was looking for something the other way. They have a webhook integration through Zapier, but I do not want to pay $20/mo for this solo feature. Maybe I will look into my bank account to see if there is a webhook. 

CNorris I should of said, the Web Logic App is not free.  Over the last 30 days it has performed 79 transactions and it has costed me £0.02 (€0.023 or $0.026).  I'm sure I could make a few more optimisations in the app's logic, but so far I have not been charged. 

berksgr Good question - just like the client apps, if the user-entered transaction is not already cleared, it will be marked cleared as part of the matching process.  If it is marked reconciled, it will stay reconciled.

Brady Great ! 🙂