UiPath · Rate Limits

Uipath Rate Limits

UiPath publishes per-organization, rolling-five-minute rate limits for the Identity Server API (Automation Cloud only — not Public Sector or Dedicated). Each HTTP method has its own ceiling. Throttled requests return HTTP 429.

5 Limits Throttle: 429
AutomationRPARate Limiting

Limits

Identity Server GET (Automation Cloud) account
requests_per_5_minutes · minute
300
300 GET requests per organization per rolling 5-minute window. Automation Cloud only — does not apply to Public Sector or Dedicated variants.
Identity Server POST (Automation Cloud) account
requests_per_5_minutes · minute
24000
24,000 POST requests per organization per rolling 5-minute window.
Identity Server PUT (Automation Cloud) account
requests_per_5_minutes · minute
160
160 PUT requests per organization per rolling 5-minute window.
Identity Server PATCH (Automation Cloud) account
requests_per_5_minutes · minute
160
160 PATCH requests per organization per rolling 5-minute window.
Identity Server DELETE (Automation Cloud) account
requests_per_5_minutes · minute
160
160 DELETE requests per organization per rolling 5-minute window.

Policies

Per-Organization Scope
Limits are enforced per organization, not per user or per application.
Rolling Window
The 5-minute evaluation window is rolling, not fixed; counters do not reset on a clock boundary.
Cloud Variants
Published Identity Server limits apply to Automation Cloud. Public Sector and Dedicated variants follow their own (separately documented) thresholds.
429 Handling
On HTTP 429, plan integration to stay within limits and apply backoff. UiPath advises designing to stay under the documented thresholds rather than relying on retry.

Sources