Netflix · Rate Limits

Netflix Rate Limits

Netflix has no publicly documented HTTP API rate limits. The retired public Catalog / Recommendations API used per-key throttling, but no current public surface exists. Internal Netflix engineering uses Hystrix / Resilience4j / Spring Cloud Netflix patterns for client-side concurrency control, but those are open-source libraries rather than rate-limit policies for an external API.

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

It captures 2 rate-limit definitions, measuring varies.

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

Tagged areas include Rate Limiting, CDN, Open Connect, and Streaming.

2 Limits Throttle: 429
Rate LimitingCDNOpen ConnectStreaming

Limits

Open Connect partner peering partner
varies
per-partner contract
Capacity / peering negotiated bilaterally with each ISP.
Device Partner Program APIs partner
varies
per-partner contract
Any APIs used by certified devices are gated behind partner credentials with contractual quotas.

Policies

Partner-onboarded access
All Netflix APIs of any kind require partner onboarding; there is no self-service public developer portal.
Client-side resilience
Netflix open-sources Hystrix, Resilience4j patterns, and Spring Cloud Netflix as the recommended pattern for clients consuming any Netflix internal service surface.

Sources