Add last_updated_after Filter to Transactions API
under review
S
Smik Lakhani
I’m building a small backup utility that periodically retrieves all my Lunch Money transactions and saves them to a Google Sheet. While implementing this, I noticed that although the API provides filtering based on a transaction’s creation date, there’s currently no way to query transactions that have been updated after a given timestamp.
For applications that sync Lunch Money data into their own database, the ability to request only transactions updated since the last sync would be extremely valuable. A last_updated_after filter would:
- Prevent repeatedly fetching the entire transaction set
- Reduce load on Lunch Money’s servers
- Improve performance for developers maintaining external sync systems
Adding this filter would make incremental sync workflows far more efficient and developer-friendly.
Log In
J
JP Shipherd
marked this post as
under review
This will also be helpful to add to a polling trigger, like in Zapier so each request only pulls new transactions since the last poll.
A
Anthony Chapligin
I'm in the process of building a reconciliation flow that will periodically go through all the transactions and update them. Having the last_updated_after would be very helpful to avoid pulling the entire history.
S
Smik Lakhani
Just to note, this wouldn’t fully solve the sync problem since deleted transactions wouldn’t be captured. Because of that, I’d still need to run an occasional full sync, but having an last_updated_after filter would still significantly reduce the overall load.