Developer API

Useful for users building out their own native apps for Lunch Money. We don't want to always be relying on a singular developer token!

Would be great to be able to manage rules, especially when ingesting from multiple sources.

GET /v2/recurring_items?start_date=…&end_date=…&include_suggested=true already returns the suggested pile — on my account that is well over a hundred suggestions against a couple dozen reviewed items. There is no way to act on any of them over the API, so triage is one browser click at a time. POST /v2/recurring_items/{id}/confirm and /reject, or a PUT that sets status, would make the pile scriptable and would pair with a read that already exists.

Be able to set individual read/write permissions for individual API keys e.g. write-only for transactions & read-only for categories for an app that should only add transactions

Access Tokens unconditionally grant global read/write permissions. It would be great if we could mint tokens with granular permissions (or even just a coarse-grained "read-only" variant) to safely limit third-party access. This is especially relevant when connecting AI agents, where granting full write capabilities can be a massive liability. For example, I ended up building a read-only MCP server[1] that filters out write endpoints at the MCP layer... but it would have been great to avoid this side-quest altogether, had there been native API-level token scope support. [1] https://github.com/daniel5151/lunch-money-mcp-ro

Would love to see more API Endpoints such as add, edit, and delete for recurring payments and other items.

Currently, the GET /transactions endpoint supports a limited set of query parameters. It isn't possible to filter on amounts or to create more complex filters that leverage AND/OR statements. If you have a use case that would benefit from better filtering when fetching transactions, please add it to the comments below. Feel free to suggest ways in which you think the new API functionality could be designed. Also, please comment on the following question: If it provided a better filtering mechanism, would you be comfortable with a POST /transactions/xxx request to get transactions? This mechanism could allow for a complex filter object to be passed in the request body. Feel free to point to examples of other APIs you like that support advanced filtering!

It would be great to make the data queryable via the API.

I want to be able to dashboard my finance. I could ask you to develop a dashboard system but wouldn't it be easier if we could connect Grafana on Lunch Money?

The API has an endpoint to create a new group from existing transactions, but not to add/remove transactions from an existing group. I like to write scripts to automate my budgeting and this would be very helpful for me! Maybe could be as simple as adding "group_id" on the create and update transaction endpoints to assign it to a group, or "group_id: false" to remove it?