webflow-rate-limits
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".
Best use case
webflow-rate-limits is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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".
Teams using webflow-rate-limits should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/webflow-rate-limits/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How webflow-rate-limits Compares
| Feature / Agent | webflow-rate-limits | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# 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 webflow = new WebflowClient({
accessToken: process.env.WEBFLOW_API_TOKEN!,
maxRetries: 3, // Default: 2. SDK uses exponential backoff.
});
// The SDK handles 429s transparently — no extra code needed
const { sites } = await webflow.sites.list();
```
### Step 2: Manual Exponential Backoff with Jitter
For operations outside the SDK or when you need custom retry logic:
```typescript
async function withBackoff<T>(
operation: () => Promise<T>,
config = {
maxRetries: 5,
baseDelayMs: 1000,
maxDelayMs: 60000,
jitterMs: 500,
}
): Promise<T> {
for (let attempt = 0; attempt <= config.maxRetries; attempt++) {
try {
return await operation();
} catch (error: any) {
const status = error.statusCode || error.status;
// Only retry on 429 (rate limit) and 5xx (server errors)
if (attempt === config.maxRetries) throw error;
if (status !== 429 && (status < 500 || status >= 600)) throw error;
// Honor Retry-After header if present
const retryAfter = error.headers?.get?.("Retry-After");
let delay: number;
if (retryAfter) {
delay = parseInt(retryAfter) * 1000;
} else {
// Exponential backoff with jitter to prevent thundering herd
const exponential = config.baseDelayMs * Math.pow(2, attempt);
const jitter = Math.random() * config.jitterMs;
delay = Math.min(exponential + jitter, config.maxDelayMs);
}
console.log(`Rate limited (attempt ${attempt + 1}). Retrying in ${delay}ms...`);
await new Promise(r => setTimeout(r, delay));
}
}
throw new Error("Unreachable");
}
// Usage
const items = await withBackoff(() =>
webflow.collections.items.listItems(collectionId)
);
```
### Step 3: Request Queue with Concurrency Control
Use `p-queue` to limit concurrent requests and prevent rate limit bursts:
```typescript
import PQueue from "p-queue";
// Webflow rate limits reset every 60 seconds
// Adjust concurrency based on your plan's limit
const queue = new PQueue({
concurrency: 5, // Max parallel requests
interval: 1000, // Time window (ms)
intervalCap: 10, // Max requests per interval
});
async function queuedRequest<T>(operation: () => Promise<T>): Promise<T> {
return queue.add(operation) as Promise<T>;
}
// Usage — requests are automatically queued and throttled
const results = await Promise.all(
collectionIds.map(id =>
queuedRequest(() => webflow.collections.items.listItems(id))
)
);
```
### Step 4: Use Bulk Endpoints to Reduce Request Count
A single bulk request counts as **one** rate limit hit but handles up to 100 items:
```typescript
// BAD: 100 individual requests = 100 rate limit counts
for (const item of items) {
await webflow.collections.items.createItem(collectionId, { fieldData: item });
}
// GOOD: 1 bulk request = 1 rate limit count
await webflow.collections.items.createItemsBulk(collectionId, {
items: items.slice(0, 100).map(item => ({ fieldData: item })),
});
```
Available bulk endpoints:
- `createItemsBulk` — Create up to 100 items
- `updateItemsBulk` — Update up to 100 items
- `deleteItemsBulk` — Delete up to 100 items
- `publishItem` — Publish multiple items by ID
### Step 5: Rate Limit Monitor
Track rate limit usage across your application:
```typescript
class RateLimitMonitor {
private remaining = Infinity;
private limit = 0;
private resetAt: Date = new Date();
updateFromHeaders(headers: Headers) {
const remaining = headers.get("X-RateLimit-Remaining");
const limit = headers.get("X-RateLimit-Limit");
const retryAfter = headers.get("Retry-After");
if (remaining) this.remaining = parseInt(remaining);
if (limit) this.limit = parseInt(limit);
if (retryAfter) {
this.resetAt = new Date(Date.now() + parseInt(retryAfter) * 1000);
}
}
shouldThrottle(): boolean {
return this.remaining < 5 && new Date() < this.resetAt;
}
async waitIfNeeded(): Promise<void> {
if (this.shouldThrottle()) {
const waitMs = Math.max(0, this.resetAt.getTime() - Date.now());
console.log(`Throttling: waiting ${waitMs}ms for rate limit reset`);
await new Promise(r => setTimeout(r, waitMs));
}
}
getStatus() {
return {
remaining: this.remaining,
limit: this.limit,
resetAt: this.resetAt.toISOString(),
throttled: this.shouldThrottle(),
};
}
}
```
### Step 6: Batch Processing Large Datasets
For operations involving thousands of items:
```typescript
async function processLargeDataset(
collectionId: string,
allItems: Array<Record<string, any>>,
batchSize = 100,
delayBetweenBatchesMs = 1000
) {
const results = { created: 0, failed: 0, errors: [] as any[] };
for (let i = 0; i < allItems.length; i += batchSize) {
const batch = allItems.slice(i, i + batchSize);
const batchNum = Math.floor(i / batchSize) + 1;
const totalBatches = Math.ceil(allItems.length / batchSize);
try {
await withBackoff(() =>
webflow.collections.items.createItemsBulk(collectionId, {
items: batch.map(item => ({ fieldData: item, isDraft: false })),
})
);
results.created += batch.length;
console.log(`Batch ${batchNum}/${totalBatches}: ${batch.length} items created`);
} catch (error) {
results.failed += batch.length;
results.errors.push({ batch: batchNum, error });
}
// Delay between batches to stay within rate limits
if (i + batchSize < allItems.length) {
await new Promise(r => setTimeout(r, delayBetweenBatchesMs));
}
}
return results;
}
```
## Output
- SDK auto-retry configured for 429 errors
- Manual backoff with Retry-After header support
- Request queue with concurrency control
- Bulk endpoints reducing request count by 100x
- Rate limit monitoring and adaptive throttling
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Persistent 429s | Too many keys sharing same plan | Reduce concurrency or upgrade plan |
| Site publish 429 | >1 publish/minute | Enforce 60s cooldown between publishes |
| Thundering herd | Multiple processes retry simultaneously | Add random jitter to backoff |
| Bulk request 400 | >100 items in batch | Cap batch size at 100 |
## Resources
- [Rate Limits Reference](https://developers.webflow.com/data/reference/rate-limits)
- [Bulk CMS Endpoints](https://developers.webflow.com/data/changelog/10232024)
- [p-queue Documentation](https://github.com/sindresorhus/p-queue)
## Next Steps
For security configuration, see `webflow-security-basics`.Related Skills
workhuman-rate-limits
Workhuman rate limits for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman rate limits".
wispr-rate-limits
Wispr Flow rate limits for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr rate limits".
windsurf-rate-limits
Understand and manage Windsurf credit system, usage limits, and model selection. Use when running out of credits, optimizing AI usage costs, or understanding the credit-per-model pricing structure. Trigger with phrases like "windsurf credits", "windsurf rate limit", "windsurf usage", "windsurf out of credits", "windsurf model costs".
webflow-webhooks-events
Implement Webflow webhook registration, signature verification, and event handling for form_submission, site_publish, ecomm_new_order, page_created, and more. Use when setting up webhook endpoints, implementing event-driven workflows, or handling Webflow notifications. Trigger with phrases like "webflow webhook", "webflow events", "webflow webhook signature", "handle webflow events", "webflow notifications".
webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
webflow-security-basics
Apply Webflow API security best practices — token management, scope least privilege, OAuth 2.0 secret rotation, webhook signature verification, and audit logging. Use when securing API tokens, implementing least privilege access, or auditing Webflow security configuration. Trigger with phrases like "webflow security", "webflow secrets", "secure webflow", "webflow API key security", "webflow token rotation".
webflow-sdk-patterns
Apply production-ready Webflow SDK patterns — singleton client, typed error handling, pagination helpers, and raw response access for the webflow-api package. Use when implementing Webflow integrations, refactoring SDK usage, or establishing team coding standards. Trigger with phrases like "webflow SDK patterns", "webflow best practices", "webflow code patterns", "idiomatic webflow", "webflow typescript".
webflow-reference-architecture
Implement Webflow reference architecture — layered project structure, client wrapper, CMS sync service, webhook handlers, and caching layer for production integrations. Trigger with phrases like "webflow architecture", "webflow project structure", "how to organize webflow", "webflow integration design", "webflow best practices".
webflow-prod-checklist
Execute Webflow production deployment checklist — token security, rate limit hardening, health checks, circuit breakers, gradual rollout, and rollback procedures. Use when deploying Webflow integrations to production or preparing for launch. Trigger with phrases like "webflow production", "deploy webflow", "webflow go-live", "webflow launch checklist", "webflow production ready".
webflow-performance-tuning
Optimize Webflow API performance with response caching, bulk endpoint batching, CDN-cached live item reads, pagination optimization, and connection pooling. Use when experiencing slow API responses or optimizing request throughput. Trigger with phrases like "webflow performance", "optimize webflow", "webflow latency", "webflow caching", "webflow slow", "webflow batch".
webflow-observability
Set up observability for Webflow integrations — Prometheus metrics for API calls, OpenTelemetry tracing, structured logging with pino, Grafana dashboards, and alerting for rate limits, errors, and latency. Trigger with phrases like "webflow monitoring", "webflow metrics", "webflow observability", "monitor webflow", "webflow alerts", "webflow tracing".
webflow-multi-env-setup
Configure Webflow across development, staging, and production environments with per-environment API tokens, site IDs, and secret management via Vault/AWS/GCP. Trigger with phrases like "webflow environments", "webflow staging", "webflow dev prod", "webflow environment setup", "webflow config by env".