Hi
While working with the bank_transactions endpoint, I’ve observed that the from_date and updated_since parameters appear to override each other when used together.
For example, when making an API call using only the updated_since parameter (with a date in the future), the response returns zero results, which is as expected:
https://api.freeagent.com/v2/bank_transactions?bank_account=771561&updated_since=2025-06-15T09:00:00.000Z&page=1&per_page=10
However, when I include both updated_since and from_date, the response includes results (with X-Total-Count = 92), suggesting that the from_date parameter is overriding or negating the updated_since filter:
https://api.freeagent.com/v2/bank_transactions?bank_account=771561&updated_since=2025-06-15T09:00:00.000Z&page=1&per_page=10&from_date=2025-05-02
As these parameters serve different purposes—from_date for the posting date and updated_since for data changes. It would be very helpful if they could be used in conjunction, such that the results are filtered by both criteria (e.g., transactions with a posting date after X and updated since Y).
Our use case involves setting an import start date in our database to allow users to choose when to begin syncing data from FreeAgent. Additionally, we rely on updated_since to avoid importing transactions already retrieved in previous syncs.
Could you please confirm whether this is the intended behaviour, or if there’s a recommended approach for combining these filters?
In the meantime, it may be worth updating the documentation to make it clear that these filters cannot be used together.
Many thanks,
Tim
