Provide a PaginatedCounts
endpoint, which responds with an object.
The object then returns the counts of all items in endpoints that Absorb have designated as needing pagination query properties on requests.
I cannot directly assume that the following is an accurate representation of that, but it might look something LIKE this:
{
"departments": 3,
"roles": 0,
"users": 309
}
For the record - When making (eg) a paginated /users
request, the 'totalItems
' property is not returned, just an array of users that fit the pagination.
Additionally, it would be super useful to indicate which endpoints DO need (or should have) pagination queries in the API Documentation.
There is not much information within the API documentation itself on this subject, unfortunately, and if it IS elsewhere, perhaps that should really be transitioned into the 1.5 docs. :)