Hello Ali Chouikhi (Annalect),
Thanks for reaching out!
I suggest you look closely at the Graph API pagination guide - Paging Microsoft Graph data in your app and Microsoft Graph throttling guidance
Graph API endpoints return an @odata.nextLink property when pagination is triggered.
Some queries against Microsoft Graph return multiple pages of data either due to server-side paging or due to the use of the $top
query parameter to specifically limit the page size in a request. When more than one query request is required to retrieve all the results, Microsoft Graph returns an @odata.nextLink
property in the response that contains a URL to the next page of results.
For example, the following URL requests all the users in an organization with a page size of 5, specified with the $top
query parameter:
https://graph.microsoft.com/v1.0/users?$top=5
If the result contains more results, Microsoft Graph will return an @odata.nextLink
property similar to the following along with the first page of results:
"@odata.nextLink": "https://graph.microsoft.com/v1.0/users?$top=5&$skiptoken=X%274453707 ... 6633B900000000000000000000%27"
You can retrieve the next page of results by sending the URL value of the @odata.nextLink
property to Microsoft Graph.
https://graph.microsoft.com/v1.0/users?$top=5&$skiptoken=X%274453707 ... 6633B900000000000000000000%27
Microsoft Graph will continue to return a reference to the next page of results in the @odata.nextLink
property with each response until all pages of the results have been read. To read all results, you must continue to call Microsoft Graph with the @odata.nextLink
property returned in each response until the @odata.nextLink
property is no longer returned.
Hope this helps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have further questions about this answer, please click "Comment".