Vimeo OTT · Rate Limits

Vimeo Ott Rate Limits

The Vimeo OTT (VHX) API reference documents a specific rate limit on customer creation of roughly 5 requests per second, and returns HTTP 429 when a limit is exceeded. The reference does not publish a single global numeric request-rate limit for every endpoint; other endpoints are expected to be subject to fair-use throttling. List endpoints are paginated at 50 items per page by default, which bounds response size. Platform-level bandwidth and upload allowances (for example, the Enterprise plan's 60TB bandwidth and 200 upload hours per month) are quotas on the OTT service rather than API request-rate limits.

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

It captures 5 rate-limit definitions, measuring requests, items, bytes, and hours.

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

Tagged areas include OTT, Video, Streaming, Rate Limiting, and Quotas.

5 Limits Throttle: 429
OTTVideoStreamingRate LimitingQuotas

Limits

Customer Creation account
requests
~5 requests/second
Documented rate limit on POST /customers in the VHX API reference.
General API Requests account
requests
not published
No single global numeric request-rate limit is documented for all endpoints; fair-use throttling applies.
Pagination Page Size request
items
50 default
List endpoints return up to 50 items per page by default.
Bandwidth Allowance account
bytes
per plan (e.g. 60TB/month on Enterprise)
A platform quota on media delivery, not an API request-rate limit.
Upload Hours account
hours
per plan (e.g. 200 hours/month on Enterprise)
A platform quota on content ingest, not an API request-rate limit.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 (Too Many Requests) responses.
Pagination
Iterate large result sets via paginated list endpoints (50 per page by default) rather than large single requests.
Fair Use
Endpoints without a published numeric limit are subject to fair-use throttling; spread bursty writes such as customer creation across time.

Sources