Rules Endpoints
M
Minijohn
Would be great to be able to manage rules, especially when ingesting from multiple sources.
Log In
Din from Lunch Money
Merged in a post:
Add API support for managing transaction rules
E
Eric
It would be convenient to be able to add/remove/modify rules from the API. This would make managing existing Custom/Payee/Recurring Rules easier, and auditing & fixing the ~1000 existing transaction rules that I've built up over years sounds like a great task for Claude.
J
Jacob
+1. I'm working with claude code and API access to handle the bulk of maintenance for my Lunch Money account. Not having API rules access is kind of brutal. Specific use case:
A recurring bill's amount changed. I updated the recurring item in the UI, but that does not update the system rule the item auto-created, and the rule is what actually matches — so the item read correctly while the following months silently failed to link.
Over the API I can detect this (the transaction comes back with recurring_id: null) and I can repair the individual transaction, since recurring_id is writable on PUT /v2/transactions/{id}. I cannot fix the cause: there is no rules resource at any version.
Even read-only would help. GET /v2/rules alone would let a script name the misconfigured rule. Today that is only findable by opening rules one at a time in the browser.
Z
Zeb
This was marked planned since 2023. Any update? ❤
n
nirev
Please please please add this. It's a real gap in the current API, and specially bad for using AI to classify transactions
L
Luke O'Connell
Adding a technical note that I don't think has come up in this thread.
The v2 API already depends on rules internally: POST /v2/transactions accepts apply_rules: true. So the API will execute your rule set on inbound transactions but provides no way to read, audit or manage the set it just ran. That asymmetry is what makes this feel like a gap rather than a scoping decision.
Two consequences for anyone ingesting from custom sources: rules are the only part of a Lunch Money configuration that can't be exported, version-controlled or restored, and there's no programmatic way to determine which rule categorised a given transaction when something lands unexpectedly.
If full CRUD is too large for the alpha, a read-only GET /v2/rules would cover backup and audit on its own and would be a genuinely useful increment.
G
Gustav Westling
I'd love this! I have resorted to reverse-engineering the browser API to manage rules programmatically for now, but it's annoying, and requires managing user cookies.
H
Hilton Campbell
I would really like to use AI to update my rules through an MCP, just need this endpoint.
j
jsonbored
Please do this, yes! I'm building something that would really benefit from this (as would other community members!)
J
Josh Faust
Really would love this.
A
Antonio Lobato
Huge upvote here from me. In the age of LLM's, being able to have an AI go through and figure out merchant information and then also apply rules automatically is a must-have. Without it, we need to instruct AI to run every so often to manually execute rules client-side.
Load More
→