specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Automation Anywhere
providerId: automation-anywhere
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: searched
modified: '2026-09-17'
reconciled: false
notes: Automation Anywhere does not publish public per-second / per-minute rate limits for the Control
  Room API. Limits are enforced per Control Room tenant and varied by edition (Cloud vs on-prem) and
  bot count. Concrete numbers require access to the customer's Control Room admin docs.
tags:
  - RPA
  - Intelligent Automation
  - Rate Limiting
  - Throttling
  - Enterprise
description: Rate limits for the Automation Anywhere Control Room API surface (Automation 360). Limits
  are per Control Room tenant and depend on edition, license size, and underlying infrastructure.
  Public docs do not publish numeric throttles; clients should implement retry-with-backoff and
  coordinate with their Control Room admin for sustained workloads.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Control Room API Default
    scope: control-room-tenant
    metric: varies
    limit: see Control Room admin documentation
    notes: Limits scale with edition (Community, Cloud Starter, Pro, Enterprise) and Control Room size.
      Bot deployment, queue submission, and credential APIs may have separate per-endpoint limits.
  - name: Bot Deployment / Queue API
    scope: control-room-tenant
    metric: varies
    limit: bounded by configured bot pool / queue capacity
    notes: Throughput is gated by the licensed bot count rather than a request-per-second cap.
policies:
  - name: Backoff Strategy
    description: Implement exponential backoff with jitter on 429 / 503. Honor Retry-After when present.
  - name: Token / Session Reuse
    description: Authenticate once with the Control Room and reuse the bearer token until expiry rather
      than re-authenticating on every call.
  - name: Bot Capacity Sizing
    description: Sustained throughput is limited by licensed bot count and Control Room infrastructure
      sizing, not solely by API throttles. Coordinate with Automation Anywhere support to size for
      peak load.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

# --- 2026-09-17 enrichment pass: searched the published docs for real limits ---
limit_count: 0
verified:
  generated: '2026-09-17'
  method: searched
  sources:
    - https://ai-kb.automationanywhere.com/general/api-errors
    - https://docs.automationanywhere.com/r/control-room-apis/cloud-control-room-apis
  findings:
    - >-
      Enterprise Knowledge publishes a RATE_LIMITED error code returned with HTTP
      429 and a QUOTA_EXCEEDED code returned with 503, but publishes no numeric
      limit, window or burst for any scope.
    - >-
      The same error reference tells callers to "check rate limit headers in
      response" without naming a single header, so no RateLimit-* or
      X-RateLimit-* header can be recorded as documented.
    - >-
      No published numeric throttle was found for the Automation 360 Control Room
      API; throughput is bounded by licensed bot count and Control Room sizing.
  response_headers_documented: []
  exhaustion_status: 429
  error_code: RATE_LIMITED
  quota_error_code: QUOTA_EXCEEDED