How many versions does a Drive Item need until it gets paginated via Graph API?

eggy mcegg 100

If I am getting a DriveItem and expanding its versions i.e.

/drives/{id}/items/{id}?$expand=versions

How many versions will there be until pagination kicks in (in the inner versions array)? I can't find the number anywhere in the documentation. I am doing some manual tests but it's taking forever editing a file every 5 minutes.

Accepted answer

Vasil Michev 106.3K Reputation points MVP

2024-09-17T16:19:51.6733333+00:00

I'm not even sure the resource supports pagination, but in any case it seems to be OK with 200 versions. I would not recommend relying on $expand for such operations however, as the operator has some known limitations for other resources. I'd use /versions instead.
Please sign in to rate this answer.
eggy mcegg 100 Reputation points

2024-09-18T08:10:38.65+00:00

Thanks for replying. I'm trying to keep the number of calls limited so I don't get throttled by Microsoft.

Let's just assume that the number of versions starts getting paginated (even if the $expand query doesnt support pagination) after 200 versions, then would it be safe to say in my logic if the numOfVersions >= 200, then assume pagination and call /versions endpoint?

eggy mcegg 100 Reputation points

2024-09-19T12:45:20.62+00:00

Ok it seems the cutoff is 200 versions.

Yanli Jiang - MSFT 26,091 Reputation points Microsoft Vendor

2024-09-26T09:17:26.73+00:00

Thanks for your information.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How many versions does a Drive Item need until it gets paginated via Graph API?

0 additional answers

Your answer