If I have a (large) collection of resources, how can I supply a client with a paginated list?
Don't use custom pagination systems like adding a page number to the URL or query string. Instead, use link relations.
If the client want to browse through the next set of collections, it can do so by following the "next" relation link. These are defined by IANA as standard relations
- Even though it's tempting to create your own pagination scheme by "building" URLs, you should only use the information given by the API. This means, you cannot assume that the 3rd page can be found at /collection/3. If you do, your client will break as soon as the API changes its pagination behaviour.