Cisco Nexus Dashboard · Rate Limits

Cisco Nexus Rate Limits

Cisco Nexus Dashboard, NX-API, and the underlying NX-OS / ACI APIs are deployed by the customer on premises or in their VPC. Public per-second rate limits are not published; throughput is bounded by switch CPU / supervisor capacity and by NX-API session limits configured in NX-OS. Streaming telemetry (gRPC/gNMI/Model-Driven Telemetry) is the recommended path for high-volume observability rather than polling REST endpoints.

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

It captures 3 rate-limit definitions, measuring concurrent_sessions, concurrent_subscriptions, and varies.

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

Tagged areas include Data Center, Networking, and Rate Limiting.

3 Limits Throttle: 429
Data CenterNetworkingRate Limiting

Limits

NX-API REST sessions switch
concurrent_sessions
see NX-OS Programmability Guide; bounded by supervisor CPU
gRPC / Model-Driven Telemetry subscriptions switch
concurrent_subscriptions
see NX-OS Programmability Guide; varies by platform (e.g. N9K-C93180YC-FX vs N9K-C9508)
Nexus Dashboard cluster API cluster
varies
see Nexus Dashboard scale guide for the deployed cluster size

Policies

Capacity-bounded
Limits are bounded by supervisor / control-plane CPU on each switch and by the Nexus Dashboard cluster's compute footprint, not by a cloud-style per-second quota.
Prefer streaming telemetry
For monitoring at scale, use gRPC/gNMI Model-Driven Telemetry instead of polling NX-API REST endpoints to avoid control-plane saturation.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429/503 responses and limit concurrent NX-API sessions per switch.

Sources