I have found the same thing, unlike the saved search api, there is no shortcut to target a particular transaction type with the Query API, so you do need to query Transaction, and add a condition for Type. I have also found that certain fields which could be included in filters in the search api, gave me the same error you are seeing when I tried to use them in the Query API. I assume they are either limitations or bugs in the new API. Make sure that you are able to set up a workbook manually through the UI for the search you are trying to build. If the UI won't let you do it, the script api probably will not either.