Webflow API and Documentation · Rate Limits

Webflow Api And Documentation Webflow Rate Limits

The Webflow Data API enforces a per-API-key, per-minute rate limit that scales by the site's subscription tier. Limits are scoped to the API key — distinct keys on the same site have independent budgets. Cached reads through the content-delivery API are effectively unlimited; Site Publish has its own one-per-minute cap regardless of plan.

Webflow Api And Documentation Webflow Rate Limits is the machine-readable rate-limit profile for Webflow API and Documentation on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests_per_minute and varies.

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

Tagged areas include CMS, Content Management, Ecommerce, No-Code, and Publishing.

5 Limits Throttle: 429
CMSContent ManagementEcommerceNo-CodePublishingWeb DevelopmentRate Limiting

Limits

Starter / Basic Site Plans key
requests_per_minute · minute
60
Per API key.
CMS / Ecommerce / Business Site Plans key
requests_per_minute · minute
120
Per API key.
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
One successful publish per site per minute.
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
Each API key has its own rate budget. Use one key per environment / app to isolate noisy clients.
429 Handling
On throttle, the API returns 429 with a Retry-After header (typically 60 seconds). Webflow's official SDK implements exponential backoff automatically.
Webhooks Over Polling
Webflow recommends webhook subscriptions for change notifications instead of polling to stay within the per-minute budget.

Sources