webflow-rate-limits

Solid

Handle Webflow Data API v2 rate limits — per-key limits, Retry-After headers, exponential backoff, request queuing, and bulk endpoint optimization. Use when hitting 429 errors, implementing retry logic, or optimizing API request throughput. Trigger with phrases like "webflow rate limit", "webflow throttling", "webflow 429", "webflow retry", "webflow backoff", "webflow too many requests".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Webflow Rate Limits ## Overview Handle Webflow Data API v2 rate limits using the SDK's built-in retry, manual backoff strategies, request queuing, and bulk endpoints to maximize throughput without hitting 429 errors. ## Prerequisites - `webflow-api` SDK installed - Understanding of async/await patterns - Knowledge of your site plan's rate limits ## Webflow Rate Limit Rules ### Per-Key Rate Limits Rate limits are applied **per API key** (not per site or per user). Each token has its own independent rate limit counter. | Rule | Details | |------|---------| | Scope | Per API key | | Reset window | 60 seconds (Retry-After header) | | CDN-cached requests | Do **not** count against rate limits | | Bulk endpoints | 1 request = 1 rate limit count (up to 100 items) | | Site publish | Max 1 successful publish per minute | | Webhook registrations | Max 75 per `triggerType` per site | ### Rate Limit Response Headers | Header | Description | |--------|-------------| | `X-RateLimit-Limit` | Max requests allowed in the window | | `X-RateLimit-Remaining` | Requests remaining in current window | | `Retry-After` | Seconds to wait before retrying (on 429) | ### 429 Response ```json { "code": "rate_limit", "message": "Rate limit exceeded. Please retry after 60 seconds." } ``` ## Instructions ### Step 1: SDK Built-In Retry The `webflow-api` SDK automatically retries 429 and 5xx errors with exponential backoff: ```typescript import { WebflowClient } from "webflow-api"; const...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

figma-rate-limits

Handle Figma REST API rate limits with exponential backoff and request queuing. Use when encountering 429 errors, implementing retry logic, or optimizing API request throughput for Figma. Trigger with phrases like "figma rate limit", "figma throttling", "figma 429", "figma retry", "figma backoff".

2,266 Updated today
jeremylongshore
AI & Automation Featured

apify-rate-limits

Handle Apify API rate limits with proper backoff and request queuing. Use when hitting 429 errors, optimizing API request throughput, or implementing rate-aware client wrappers. Trigger: "apify rate limit", "apify throttling", "apify 429", "apify retry", "apify backoff", "too many requests apify".

2,266 Updated today
jeremylongshore
AI & Automation Featured

adobe-rate-limits

Implement Adobe API rate limiting, backoff, and quota management across Firefly, PDF Services, Photoshop, and I/O Events APIs. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Adobe. Trigger with phrases like "adobe rate limit", "adobe throttling", "adobe 429", "adobe retry", "adobe backoff", "adobe quota".

2,266 Updated today
jeremylongshore
AI & Automation Featured

klaviyo-rate-limits

Implement Klaviyo rate limiting, backoff, and request queuing patterns. Use when handling 429 errors, implementing retry logic, or optimizing API request throughput for Klaviyo. Trigger with phrases like "klaviyo rate limit", "klaviyo throttling", "klaviyo 429", "klaviyo retry", "klaviyo backoff", "klaviyo Retry-After".

2,266 Updated today
jeremylongshore
AI & Automation Featured

customerio-rate-limits

Implement Customer.io rate limiting and backoff. Use when handling high-volume API calls, implementing retry logic, or hitting 429 errors. Trigger: "customer.io rate limit", "customer.io throttle", "customer.io 429", "customer.io backoff", "customer.io too many requests".

2,266 Updated today
jeremylongshore