Vimeo rate limits are dynamic; use the fields parameter to stay under

Vimeo API rate limits vary with the authenticated end user’s membership. Request only needed fields with fields=..., cache repeated reads, and watch X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset.

The current Vimeo guide says field filtering doubles the normal quota; it also documents HTTP 429 while a user is over quota. Tune polling from the returned headers instead of relying on a fixed request-per-minute range. Each token’s quota is tied to its end user; unauthenticated calls use the app owner’s quota.

Vimeo’s current rate-limit guide (API 3.4) documents membership-based authenticated per-user limits, field filtering doubling quota, the three rate-limit response headers, and HTTP 429 during cooldown. This replaces the previous third-party 100–2000 range, which is not the current official model. Source: https://developer.vimeo.com/guidelines/rate-limiting