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: Citrix NetScaler
providerId: citrix-netscaler
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: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Application Delivery Controller
  - Load Balancing
  - API Gateway
  - Rate Limiting
description: >-
  NetScaler is a customer-deployed appliance (MPX / VPX / SDX / CPX) plus the NetScaler Console
  (ADM) management plane. The NITRO REST/JSON API is the primary management interface; throughput
  is bounded by the appliance's management-CPU and the licensed throughput tier rather than a
  cloud-style per-second quota. NetScaler itself can also enforce data-plane rate-limit and
  responder policies on the customer's traffic, configured per virtual server.
notes: Numbers below are descriptive placeholders. Replace with per-platform NITRO management
  throughput from the NetScaler ADC documentation for the deployed version (e.g. 13.1 / 14.1).
sources:
  - https://docs.netscaler.com/en-us/citrix-adc/current-release/nitro-api.html
  - https://docs.netscaler.com/en-us/citrix-adc/current-release/appexpert/rate-limiting.html
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: NITRO management API
    scope: appliance
    metric: varies
    limit: bounded by NetScaler management-CPU and platform
  - name: NetScaler Console (ADM) API
    scope: tenant
    metric: varies
    limit: see NetScaler Console scale guide for the deployed cluster size
  - name: Data-plane rate limiting
    scope: virtual_server
    metric: configurable
    limit: configured per virtual-server / responder policy by the appliance administrator
policies:
  - name: Capacity-bounded
    description: Management throughput is bounded by appliance CPU and the licensed throughput tier,
      not by a cloud-style per-second quota.
  - name: Bulk operations
    description: Use NITRO bulk endpoints rather than per-resource calls for large config changes.
  - name: Backoff Strategy
    description: Implement exponential backoff with jitter on HTTP 429/503 responses from NITRO and
      NetScaler Console APIs.
  - name: Token reuse
    description: Reuse session tokens until expiry; do not log in per request, which floods the
      management plane.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com