Paging with id (token) instead offset number #411
Description
Describe the change
Support token based paging. We should support to fetch resources from a specific id which is a cursor in this case.
Current situation
Currently paging for all endpoints is supported using offset:x while x is a number.
Should
Offset should accept an id which is most likely the resource id. Since the resource id contains the date/time it is possible to retrieve all resources > _id.
Due backwards compatibility offset should probably accept a number as well.