The API has the ability to return a link to the next page of results. For example, through the next_page parameter.
It seems that this approach simplifies something, but rather no than yes: on the client, the request to the first page has already been formed, so there is no special difficulty to do on the next one, but on the server this is a completely new code:
- you need to find out the public name of your host (by default we do not know)
- you need to add serialization of the accepted parameters (initially there is no such code)
So, it is better without the next_page parameter, just return total_count so that it is clear whether there are more pages or not.