When requesting information that FreshService paginates (example: All tickets), no information is returned in the header to show how many total results or total pages of information there are.
This ultimately results in a requirement that a number of additional information is determined in consuming the API.
For example, to retrieve all paginated information, one would have to request the first page and determine if the request returned a body with 30 items. If the body does have 30 items, modify the URI being requested and test that result.
That could provide 1 of 3 results.
1. An empty response, signifying that there was exactly 30 items in this view.
2. A result with less than 30 items, signifying that there are no more pages to consume.
3. A result with 30 items, which requires additional requests to determine if there was exactly 60 (or any multiple of 30) items that matched or if there is indeed other pages, looping through the same steps.
This could result in a number of additional and unnecessary requests to the FS API as well as the additional overhead and testing by the consumer.
Inclusion of a Link header or an X-Total-Count could provide this information without changing or breaking existing functionality.
Some information:
https://developer.github.com/v3/#pagination
http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api#pagination
