Citrix · Rate Limits

Citrix Rate Limits

Citrix Cloud and Citrix DaaS REST APIs are governed by per-customer service throttles in the Citrix Cloud control plane. Specific per-second / per-minute thresholds are not published in self-serve form; clients should rely on HTTP 429 / Retry-After signaling and request increases via Citrix support. On-premises NetScaler / ADC NITRO and the Workspace API have their own throttling that is bounded by appliance / control-plane capacity.

Citrix Rate Limits is the machine-readable rate-limit profile for Citrix on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring varies.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Application Delivery, Desktop-As-A-Service, Workspace, and Rate Limiting.

3 Limits Throttle: 429
Application DeliveryDesktop-As-A-ServiceWorkspaceRate Limiting

Limits

Citrix Cloud / DaaS REST API customer
varies
see developer.cloud.com; per-service throttles applied per customer
NetScaler NITRO API appliance
varies
bounded by NetScaler control-plane CPU; see Citrix ADC documentation
Workspace / StoreFront APIs site
varies
see Citrix Workspace developer docs

Policies

Backoff Strategy
Implement exponential backoff with jitter on HTTP 429/503 responses and honor any Retry-After header.
Bearer token reuse
Cache Citrix Cloud bearer tokens until expiry; do not request a new token per call.
Pagination
Use cursor / pagination parameters on list endpoints rather than polling full collections.
Limit increase
Production tenants requiring higher throughput should engage Citrix support with the Customer ID and traffic profile.

Sources