Pagination, sorting, filtering

Most APIs accessible in the Qlik platform applies pagination, sorting, and filtering. For example, this means that you need to navigate resources by making multiple requests to retrieve additional entries, but you also have the possibility to both define sort order and filter entries at the same time. Each concept is described in detail in the following sections.


The Qlik platform uses a concept called cursor-based pagination. This concept revolves around unique values generated for each page in the dataset instead of using plain numeric pages. This ensures consistency when fetching multiple pages in a concurrency system, where plain page numbers might skip or add entities in-between pages if there are changes during the pagination process. Another, perhaps even more important aspect, is that it ensures good performance both for you as an end-user and for the APIs handling the request because there is no need to interact more than necessary with the underlying database.

The cursors are arbitrary unique string values and can't be calculated client-side, in other words you must use the pagination links sent to you by the API.

An example of such a request and response:

> GET /api/v1/items?limit=3 HTTP/1.1
> host:
> authorization: bearer xyz
> accept: application/json

This requests the first page of items, with a limit of three items per page.

The response looks something like this:

< HTTP/1.1 200
< content-type: application/json
< content-length: 123

  "data": ["list", "of", "items"],
  "links": {
    "prev": { "href": null },
    "next": { "href": "<next-cursor>" },

To fetch the next page, use the value in your request.


When fetching lists of resources it often makes sense to sort on fields of interest to you. While each resource may vary a bit in terms of which fields you may sort on, the following guidelines should help you understand the concept. To see which sort options you have for a specific resource, consult the API reference page for it which should include that information.

Sorting is defined in query parameters, specifically the ?sort= query parameter. Each sort criteria may use + and - signs as a prefix to apply ascending or descending order. You may also supply multiple criterias by comma-separating the fields. Here's an example that sort title by ascending order, and description by descending order:

> GET /api/v1/items?sort=+title,-description HTTP/1.1
> host:
> authorization: bearer xyz
> accept: application/json


Not available at this time.

Was this page helpful?