Developer API

Return more descriptive error messages so users can figure out what's going wrong

Get transactions for multiple tags (an OR condition between a few tags)

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.

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

I'm trying to implement an "infinite scroll" transactions page but items returned by "v1/transactions" are not sorted by date (probably by id) and the UX is bumpy. Would be nice to add a sort parameter (if not to compute intensive). PS: as a workaround I'm paginating the query by week and it's seems to work.

For users who have accounts with different currencies, it would be useful if account objects returned by the API had properties that show the balances in the primary currency as well. This feature appears to have been implemented in the GUI: https://feedback.lunchmoney.app/overview/p/show-currency-conversions-on-accounts , so perhaps the data is there and just needs to be exposed in the API?

For users who manage transactions primarily by the API, it would be useful to have the ability to disable manual (non-API-driven) changes to an asset so that it's not possible to accidentally edit the amount of a transaction, etc. in the GUI for those accounts.

Rules do not seem to be applied to transactions inserted via a POST /transactions request even when the apply_rules query parameter is set to true. You can replicate this by manually creating a transaction that triggers an existing rule (for example to change the payee name) and see it immediately take effect. After inserting a transaction that should trigger the rule, and viewing transaction the change does not take place, but will if you choose the "Apply Rule" option from the rules page.