We agree. In order to query Contacts or Transactions via the API, ALL entities must be pulled currently which takes time and resources. API calls need to be able to filter, either with URL parameters , or a body request something like: {"parameter":"created_date","operator":"greaterthan","value":"1/1/2025"} A body request would allow for more options to be used. We have need to filter Transactions by giftDate, createdDate, checkDepositDate, method. If those options were available, then we could pull only a relatively few transactions that we need to complete tasks, update, report on rather than pulling the entire database of transactions to find the ones we want.

Related Feature Request Feedback on https://community.givebutter.com/integration-requests/p/api-supporting-querying-transactions-by-date

This is an important feature when querying contacts or transactions as now the API will get all transactions or contacts and this in my case takes about 2 minutes and is tying up resources on the backend. In my case, we are using an API to recall transactions from a given date range and don't need all transactions from the beginning of time. Also, this means we have to add additional code to the API to filter the data. Very inefficient.

Upvoting this. Being able to filter by Last Updated At would also be very useful to ensure data is kept in sync across systems.