Scott Robertson It's on the list! "payee_name" will be able to be passed to the writable transaction endpoints to resolve an existing payee (by name) or create a new one if it does not exist. ETA: mid-next week.
Scott Robertson That's a good idea to allow setting the category (if not specified) by the payee. We store "category autofill" setting for each payee, based on previous categorization so I think this would be feasible. I'll add it to our list. I can't promise but it seems fairly straightforward to implement and would be helpful.
Scott Robertson Oh yeah, that would certainly reduce the need for that logic! By the way, I like your project! The new possibilities being opened up by PSD2 are really neat and it's fun to see projects like your's starting to take advantage of it.
Brady at YNAB Thank you :) Really looking forward to all the PSD2 stuff, which is why i am super excited about the bulk endpoint! Gonna integrate teller.io next once we have the duplicate detection working in a bit nicer/more reliable way which opens things up to a huge amount more banks.
Scott Robertson Initially no - the payee_name specified would be used to create or use an existing payee by that name. We have "payee rename rules" for Direct Import which allows for imported payees being renamed in YNAB to be remembered and used going forward. To use these through the API, we'd need to implement it. I'll add it to the request list.
Brady Bit late to the API beta, but enjoying playing around with it! Thanks for all your hard work. This payee renaming functionality in the API is exactly what I'm looking for – any follow-up about whether it is being implemented?
Thomas Kilgour Thanks for the feedback! It hasn't been implemented yet but it's still on the list. It would certainly be a handy thing to have in the API. I can't give you a definitive answer on if/when it will be implemented but I think it's likely we'll get it added in the not-too-distant future.