thimble.mozilla.org | longer maintained. Please check | Learning library

The API has to support pagination in the sense that it should be able to respond to queries with fragments of data, instead of dumping all the data in one go.

For example:

For page 1: your.api.endpoint/your/resource/path/countries?offset=0&pageSize=50

For page 4: your.api.endpoint/your/resource/path/countries?offset=200&pageSize=50

You can build your URL params for pagination however you want though, e.g. /countries?pageNo=4&pageSize=50, /countries?from=200&to=250 etc.

Note:

When you implement server-side pagination, you need to implement server-side sorting and filtering too; that's because with server-side pagination the client can only see 1 page of data and therefore sorting or filtering would be inaccurate.

EDIT to show example of mocking API response

In your service you might have something like this: