When Microsoft Graph requests return too much information to show on one page, you can use paging to break the information into manageable chunks.
You can page forward and backward in Microsoft Graph responses. A response that contains paged results will include a skip token (odata.nextLink) that allows you to get the next page of results. This skip token can be combined with a previous-page=true query argument to page backward.
The follow request example shows paging forward:
The $skiptoken parameter from the previous response is included, and allows you to get the next page of results.
The following request example shows paging backward:
The $skiptoken parameter from the previous response is included. When this is combined with the &previous-page=true parameter, the previous page of results will be retrieved.
The following are the request/response steps to page forward and backward:
The following restrictions apply to paged requests: