where
argument limits the resulting document list using search criteria applied against indexed properties.sort=total
, or a JSON object containing
one or more property names with either 1 (ascending) or -1 (descending) as the value.skip=100
, you would receive results 101-200.skipskip
should only be used for small result sets of a few hundred or less. For paging larger result sets, see Paging.limit=2
. The default limit for an API request is 100. The max limit is 1000.hasMore
property when it is true
. Paging results can be accomplished using limit
and where
query arguments or a combination of where
, limit
and skip
query arguments._id
, sorting by the identifier and applying a where argument. For example:name.last
, it is possible to fall back on using the skip
argument for paging, though it is not as efficient as using a unique indexed field. Additionally, paging using skip
is only effective for small result sets (e.g. less than a few hundred records).GET /conversations?paths[]=_id&limit=2&sort={"_id": 1}
results in the following response:hasMore
property is true, so the caller knows there are more results. The last _id
in the list is used in the next where
argument like this: