Rate limit quotas for Sharepoint REST APIs

Question

Rate limit quotas for Sharepoint REST APIs

Rick Huang 61

We see that there are explicit resource unit limits defined for Microsoft Graph APIs for files / lists in Sharepoint applications, e.g. https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#application-throttling.

However, we require use of Sharepoint REST APIs for additional Sharepoint specific data unsupported by the Graph API, e.g. Sharepoint site page web parts, Sharepoint hidden groups + group members on sites, etc. Are there rough resource cost / limits across apps / tenants for Sharepoint REST APIs we can use to adjust our QPS accordingly, and are these shared with Graph APIs?

1 answer

Your answer

Answer 1

Rob Windsor 2,001

The answers to your questions are covered in the document you linked. In the highlighted sections "CSOM and REST" means the SharePoint Client Object Model and the SharePoint REST API.

Rick Huang 61 Reputation points

2022-09-09T16:08:36.69+00:00

It wasn't too clear to me how the two interacted-- the first blurb did mention that all 3 APIs count toward the application's usage, but the second blurb mentions that there isn't a predetermined resource unit cost for CSOM/REST, although the linked section mentioned a predetermined rough resource unit cost for a particular Graph API endpoint.

Is it possible to clarify a bit more how all 3 APIs count toward an application usage while 2/3 of the APIs don't have a predetermined resource unit cost, and only the Graph API endpoint has an explicit limit for its set of APIs?
Rob Windsor 2,001 Reputation points

2022-09-10T10:54:53.45+00:00

As far as I know that document provides all the detail that Microsoft has shared on how they determine if an application will be throttled. In other words, I'm not aware of any way to predetermine if an application might be throttled. Because of this, the standard practice is to always check for 429 and 503 errors and then use the Retry-After header to determine how long to wait to resubmit the request.
Tong Zhang_MSFT 9,251 Reputation points

2022-09-13T07:37:19.84+00:00

Hi @Rick Huang ,

Do you have any further questions about this thread? If you have any questions or progress, you can contact me in time.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Rick Huang 61 Reputation points

2022-09-13T16:11:57.097+00:00

Hey @Tong Zhang_MSFT ,

Thanks for the response. The open question on this thread is still on how the REST API endpoints interact with the resource buckets for the Graph APIs, since the documentation notes REST API endpoints have different costs, but the documentation only includes info on the Graph API specific endpoint costs.

SharePoint provides various APIs. Different APIs have different costs depending on the complexity of the API. The cost of APIs is normalized by SharePoint and expressed by resource units. Application’s limits are also defined using resource units.

Additionally, we noticed this blurb:

Although each application has its own limits within a tenant and we allow tenants to run more than one application, multiple applications running against the same tenant share the same resource bucket, and in rare occurrences can cause rate limiting when too many applications send requests at the time.

It seems that there are only published rate limits per (app, tenant) combination, rather than all apps for a single tenant, in the existing documentation page previously linked. Are the limits published across all apps for a tenant as well?

Share via

Rate limit quotas for Sharepoint REST APIs

1 answer

Your answer