API throttling is the process of limiting the number of API requests a user can make in a certain period. An application programming interface (API) functions as a gateway between a user and a software application. Most servers implement various types of throttling for protection of their internal stability.
SharePoint Online uses throttling to maintain optimal performance and reliability of the SharePoint Online service. The throttling feature controls the number of API calls or operations within a time window to prevent overuse of resources. When your application gets throttled, SharePoint Online returns a HTTP status code 429 (“Too many requests”) or 503 (“Server Too Busy”) and the requests will fail.
Confluence limits the rate of REST API requests to ensure that services are reliable and responsive for customers. Rate limiting is not used to differentiate levels of service to different types of customers or apps. Rate limiting is implemented as a set of rules that consider the number of threads handling certain kinds of requests, the cost of the requests, and the resources required by the requests. Each rule applies to a unique combination of resources such as nodes, tenants, database hosts, endpoints, or compute resources. Rules are evaluated in a sequence designed to maximize computational efficiency.
Enterprise Bridge follows recommendations of every service provider, such Microsoft®, Atlassian® and other vendors to avoid throttling and optimize access to respective API. Enterprise Bridge offers a setting for limiting API calls to avoid overload of connected services and avoid throttling.
