Sometimes a plain ole' query won't do the trick. Technically, every filter added at the root level is equivalent to using an "AND" statement. This syntax can be really limiting depending on use case. From the very start, we knew more flexibility around input queries would be needed power the very best of applications across multiple industries, and that's why we have the following options to help you really get your queries targeted:
- "and" (compound queries) - stack multiple locations & introduce "AND" and "OR" statements
- "exclude" - remove properties from search results based on your specified criteria
- "exists" - control whether properties are returned based on the existence of a field (e.g. House number ("house") must be populated)
- "sort" - order your search results by specific response field values done on our server side
- "filter" - an extension of "exclude" so that you can exclude more than 1000 entries in one API call