Unfortunately, @Diakoptis is correct, this filter is not implemented - neither documented nor in our code so the only recourse at this time is to filter it client-side. @Blake_Hickman is also right in that I agree with the statement “I feel like this should be a basic function.” The challenge here is with
If I can do that with a custom field, why can I not do that with a built-in field like due_on?
Well, you can’t pull that query off in our API either, only in our web app, for what it’s worth . The reason that this doesn’t just come out of the box is that the underlying infrastructure for our in-app search is different than that of the rest of the app - this is actually pretty common, for example, Apache Lucene and Amazon ElasticSearch are examples of such systems. While this is how our search works, we haven’t taken advantage of this anywhere in our API yet.
Our API team has definitely been thinking about this and capturing all the search and filtering use cases (I forwarded this one on!) to help define what that would look like in our API. We haven’t built it out yet, so I don’t have a date to share but it’s definitely fresh in our minds!