Microsoft Project Rate Limits
Microsoft Project Online APIs are hosted on SharePoint Online, so they inherit SharePoint's per-user / per-tenant throttling, plus Power Platform request limits via the Microsoft 365 license category. Limits are enforced via 429 / 503 responses with Retry-After headers; clients must honor the header. There is no published per-second cap — Microsoft uses a dynamic algorithm based on resource consumption.
Microsoft Project Rate Limits is the machine-readable rate-limit profile for Microsoft Project on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring varies and requests_per_day.
Limit state is signalled in the retryAfter, ratelimitLimit, ratelimitRemaining, and ratelimitReset response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.
Tagged areas include Rate Limiting, Project Management, Microsoft, and SharePoint.
retryAfterratelimitLimitratelimitRemainingratelimitReset
generated, dated 2026-05-05.
Limits
Policies
Sources
- https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online
- https://learn.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.