You cannot list/download all of your collection's resources at once: there can be too many.
So we provided you with standard scrolling features: as soon as you finish fetching a set of resources, you can trigger a second API call to fetch next resources according to the ordering configuration you are using in the request, then a third API call and so on.
The largest possible set of resources returned at one contains up to 25 resources and it's the default choice we provide to you. This means that if you have less than 25 resources in a collection, you don't have to worry about resources scrolling at all. However, when you have more than 25 resources in a collection, you'll need to download first 25 and then ask for resources from 26 to 50, and so on with 51 to 75 up to the totality of your resources.
Responses to listing endpoint are ordered lists of resources, according to sorting criteria and sorting direction.
If a request wasn't specifying any criteria and any direction (see Sorting collections), default values apply for sorting, depending on the collection's nature.
limit parameter is provided in all endpoints returning a collection of resources.
Such parameter is valued 25 (maximum) as default, but you can change with smaller values if you want your collection to be returned in more batches.
Do not rely on max limit
Please mind we reserve the ability to change anytime the maximum number of resources returned in a single listing request.
last parameter is provided in all endpoints returning a collection of resources.
Such parameter is not valued by default, but you can change it with the last id you fetched from the previous API listing request so that the current API request will return next set of resources according to the sorting criteria and direction you specified, starting from
last (excluded) onward.