Nutanix · Rate Limits

Nutanix Rate Limits

Nutanix APIs (Prism Central v3/v4, Prism Element v2, Karbon, NDB, NC2, NCM Self-Service, Foundation) are deployed within customer-controlled clusters and do not have public per-tier rate limits. Throughput is bounded by the cluster's CPU/memory/network and Prism Central's task queue. Long-running operations are returned as task UUIDs for asynchronous polling. Public docs do not publish numeric per-second ceilings.

Nutanix Rate Limits is the machine-readable rate-limit profile for Nutanix 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 unauthorized, forbidden, throttled, and serviceUnavailable.

Tagged areas include Cloud Management, Hyperconverged, Infrastructure, Virtualization, and Kubernetes.

3 Limits Throttle: 429
Cloud ManagementHyperconvergedInfrastructureVirtualizationKubernetesDatabaseRate Limiting

Limits

Prism Central / Prism Element cluster
varies
cluster-bounded; not numerically published. Use task-based polling for long ops.
NCM Self-Service / Karbon / NDB / Foundation cluster
varies
cluster-bounded; defer to product-specific docs
Nutanix Cloud Clusters (NC2) tenant
varies
see Nutanix portal documentation

Policies

Async tasks
Most write operations on Prism return a task UUID; clients should poll the tasks endpoint for completion rather than blocking on the request.
Authentication
Prism uses Basic auth or API key over HTTPS; v4 supports key-based auth via Prism Central service accounts.
Backoff
Implement exponential backoff with jitter on 429/503 and respect Retry-After when present.
Cluster capacity
Effective rate is bounded by the cluster's CPU and Prism Central scheduler; sustained heavy automation should batch and pace requests.

Sources