Webflow · Rate Limits

Webflow Rate Limits

Webflow's Data API enforces a per-API-key, per-minute rate limit that scales with the site's subscription tier. Limits are scoped to the API key (each key has its own budget); cached reads against the content-delivery API are effectively unlimited. The Site Publish endpoint adds a hard "one successful publish per minute" limit on top of the per-minute call budget.

5 Limits Throttle: 429
CMSEcommerceNo-CodeWeb DevelopmentRate Limiting

Limits

Starter / Basic Site Plans key
requests_per_minute · minute
60
Per API key, on Starter and Basic Site plans.
CMS / Ecommerce / Business Site Plans key
requests_per_minute · minute
120
Per API key, on CMS, Ecommerce, and Business Site plans.
Enterprise Site Plans key
requests_per_minute
-1
Custom rate limit negotiated as part of the Enterprise contract.
Site Publish site
requests_per_minute · minute
1
At most one successful publish per site per minute, regardless of plan.
Cached Content-Delivery Reads key
varies
effectively unlimited
Cached requests served by the content-delivery API are not subject to the per-minute API rate limit.

Policies

Per-Key Scoping
Rate limits are applied per API key. Different keys on the same site have independent budgets, so per-environment / per-app keys can be used to isolate noisy clients.
429 Handling
When throttled, the API returns 429 with a Retry-After header (typically 60 seconds). The official Webflow SDK implements exponential backoff automatically.
Webhooks Over Polling
Webflow recommends webhook subscriptions for change notifications instead of polling to keep within the per-minute budget.

Sources