Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
← Back to post

Revisions 2

3 years ago
Is the Q2 Central API LookupUser operation response being limited?
Is the LookupUser operation response being limited?
Is the LookupUser operation response being limited?

Hello. I'm curious if there is an undocumented restriction to the number of objects returned in the LookupUser operation's 'Data' response array? the documentation does not identify any parameters for use with pagination or limiting the response. I am not sending any restrictions on records in my call. However, I only receive a maximum of 10 users for customers who show more than this in Q2 Central.
#