Add complete API support for recurring items
I
Ian
Would love to see more API Endpoints such as add, edit, and delete for recurring payments and other items.
Log In
A
Adam
Here's my insane worldview: No one wants to use your company's interface (not "you" as in Lunch Money—"you" as in all software ever created.) With AI, the value a company provides is no longer in its interfaces, it's in the "engine" it provides.
As software gets more and more personalized with AI agents, it makes sense to support Agents as a first-class citizen. I'm not the first to propose this idea, but I think Lunch Money's ethos of allowing people to customize their platform fits perfectly with this view. In fact, it's a unique selling point no other finance platform has as far as I'm aware (it's what brought me _back_ from YNAB!)
So, my request is that anything I can do in the UI, I can do via the API (an agent.) I build my own "personal interface" by defining how I allow my agent to interact with Lunch Money. Recurring Items aren't currently supported via the API, so I have to resort to using the internal APIs right now (which sometimes results in bugs: https://feedback.lunchmoney.app/bugs/p/api-created-recurring-items-not-shown-or-deletable-in-ui 😬 Yes. I know this is my fault for going off the paved path!)
J
JP Shipherd
Adam thanks for the insight. In general, we agree with your perspective, which is why we have invested a lot over the last year to create an understandable API interface for most of the Lunch Money functionality surface area.
A few bits of functionality, such as linking Plaid or Synced Crypto accounts and creating Recurring Items, still don't lend themselves well to basic CRUD/REST interfaces. These functions (many of which were implemented before Lunch Money had a public API) depend on orchestration across multiple endpoints and/or 3rd-party interfaces. As a result, we STRONGLY recommend that the community DOES NOT use our internal API interfaces, as they may not work as you expect and you could potentially corrupt your data.
I do think that we can probably get to the point where we can create a public API for managing the full lifecycle of recurring items, but it will take some re-engineering of the existing system. More upvotes on this feature request will definitely help us prioritize it.
Din from Lunch Money
Merged in a post:
Manage reoccurring items via the API
T
Tim Schindler
I want to be able to perform CRUD operations on reoccurring items via the API.