Developer API

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

From Discord: yeyeh: Is it possible to define an external ID on an account (asset)? I am trying to find a way to link accounts automatically from one source to LunchMoney. Matching on account name could work but if the user decides to alter that, we lose the mapping. If there was an external ID that matched the original source, it will always work. Is there any workaround?

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!

I'm having the same problem as the one described in this Discord thread [1]. Basically I want to just create a stateless CLI that just fetches records from my banks, and call the insert endpoint with all the records found. The problem is that unless you're using strictly exclusive intervals, you'll sometimes get repeated transactions that were already inserted before by the CLI, and currently that just errors out the entire insertion operation (notably, while still returning a 200 status code). Ideally, this would instead return an error for the individual entries that were duplicated, while still inserting the rest, or alternatively, just ignore the duplicated insertions. Even better would be an upsert endpoint, which just updated or inserted based on the external_id, which would greatly simplify both development and deployment of these kinds of synchronization scripts. AFAIK, this currently forces me to insert individually (or check before insert), which is inconvenient and slow. [1]: https://discord.com/channels/842337014556262411/1220122559824003202

An OpenAPI spec would be helpful as an API developer. Benefits would include live, up-to-date docs when a new field is added as well as an easy to use SwaggerUI

Expose merchant_names endopoint, can be useful when building an autocomplete payee field.

Transactions linked to suggested recurring items return null for the transaction notes field in the API, because they inherit the notes field from the suggested recurring item. This behavior isn't documented and causes confusion. Only confirmed recurring transactions should inherit the recurring item's notes—or the documentation should clarify that suggested recurring transactions behave this way too.

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

LM being primarily a web application, I feel it should have a way to link to specific transactions. Something like: https://lunchmoney.app/transactions/TX_ID which would open a standalone view just for that transaction. Here's why this is useful: Apps using the API could sometimes want to show the link to the transaction so that the user can look at it or modify it or whatever Users that share their account (i.e. couples) could send each other links to transactions when they need to clarify something during budgeting.