Nearly all methods in the API accept the
pagesize parameters for fetching specific pages of results from the API.
page starts at and defaults to 1,
pagesize can be any value between 0 and 100 and defaults to 30.
Fetching All Results
Oftentimes an application will be interested in fetching all the items that match specific criteria, but this can be complicated when the number of matches
exceeds 100 (the maximum
pagesize). To assist in this case, the API returns the
has_more property on the common wrapper object
if there are more results to be fetched. An application can use this property to fetch all results without having to speculatively issue queries or pay for the
total property is available on the common wrapper object (but not returned by default, add it via a filter) for
cases where the count of items that match a set of constraints is more interesting than the items themselves.
total is also a useful property when displaying paging controls. In this case applications would want to include both
a filter rather than making two separate requests.
total can be equally as expensive as fetching
items. Put another way, an application fetching
total when not needed is potentially halving its performance. It is for this reason that
total is not returned by default.