Optimizely Rate Limits
Published API rate limits across the Optimizely estate. Optimizely documents limits in prose on two product docs pages (ODP and CMP) and nowhere else — and it returns NO rate-limit response headers anywhere: not one of the 28 harvested OpenAPI documents declares X-RateLimit-*, RateLimit-* or Retry-After, and only 2 of 1,606 documented error responses declare a 429 at all. An agent therefore cannot read remaining quota from an Optimizely response and must pace client-side against the numbers below.
Optimizely Rate Limits is the machine-readable rate-limit profile for Optimizely on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 8 rate-limit definitions, measuring requests_per_second and requests_per_month.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting, Experimentation, and Customer Data.