Currently, the GET /transactions endpoint supports a limited set of query parameters. It isn't possible to filter on amounts or to create more complex filters that leverage AND/OR statements.

If you have a use case that would benefit from better filtering when fetching transactions, please add it to the comments below. Feel free to suggest ways in which you think the new API functionality could be designed.

Also, please comment on the following question: If it provided a better filtering mechanism, would you be comfortable with a POST /transactions/xxx request to get transactions? This mechanism could allow for a complex filter object to be passed in the request body. Feel free to point to examples of other APIs you like that support advanced filtering!