Matching imported transactions
I developed my own interface for creating new transactions right after I pay by my credit card, and I'm using YNAB API. I'm keeping those transactions uncleared.
But when transactions are imported from the bank account official way, it is not possible to match them together. Is there any way how to mark transactions over API that is "manually inserted" and that I can match transactions later?
That's a great question! In YNAB, it's not possible to match two transactions that have both been imported--whether that's through the API, File Based Import, or Direct import, so your research is definitely correct.
Edit: I originally gave you some mis-information about transactions. Here's the correct information:
If import_id is omitted or specified as null, the transaction will be treated as a “user-entered” transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).
Here's where that's from: https://api.youneedabudget.com/v1#/Transactions/updateTransactions
(If you toggle from example to model). So, if you go ahead and use a null "import_id" you could match that transaction.
However, I think the best course of action here is for me to pass on a request to our API Developers to take a look at allowing some change to the matching logic of two imported transactions from different sources, or to treat API transactions differently than imported transactions from other sources.
Let me know if that makes sense or if I can answer some additional questions.