# Pagination, Filtering, and Sorting Many times, a large number of results could be returned when making API calls. For that reason, one need to paginate the results, alongside allowing filtering and/or sorting in specific order, to make sure responses are easier to handle. ## Pagination When available, pagination can be implemented using one or both of two query parameters: * limit to define the number of items returned in the response, and
* page to specify the *sequence* or *range* of the items list

Quable API has a default limit of 100 for results (except on /assets, /documents, /classifications, /links and /variants endpoints), and start at page 1, but it is advised to always explicitly set at least the limit parameter. ## Filtering Most API endpoints do allow basic filtering on several of their properties (one filter for one property).
Possibility to filter on multiple values by using square brackets on those qualified.
Example : /api/endpoint?id[]=value1&documentType.id[]=value2

Some of them have a generic ‘**search**‘ filter available which allow a cross-properties filtering. Those properties may change over time, without warnings, when needed.

Filters should always be used as **query parameters**.

Some of them accept a ‘**X-Quable-Locale**‘ header in order to specify the Locale on which filters must be applied. ## Sorting Sorting is determined through the use of the ‘**order**’ query string parameter.
It use the square brackets to specify the property on which the sort must apply, and the supported sort directions, either ‘**asc**’ for ascending or ‘**desc**’ for descending, as value.
Example : /api/endpoint?order[id]=asc

By default, the sort on translated properties like ‘name‘ is make on the **default language** of the PIM.
This behavior can be overridden by passing the chosen - and available - **language** in the ‘**Accept-Language**‘ header parameter of the query.

200Catalog collection