figma-rate-limits

# Figma Rate Limits ## Overview Figma uses a leaky bucket algorithm for rate limiting. When the bucket is full, the API returns 429 with a `Retry-After` header. Limits vary by plan tier, seat type, and endpoint tier. ## Prerequisites - Figma REST API integration working - Understanding of async/await patterns ## Instructions ### Step 1: Understand the Rate Limit Model **Endpoint tiers** (limits are per-user, per-minute): | Tier | Endpoints | Typical Limit | |------|-----------|--------------| | Tier 1 | `GET /v1/files`, `GET /v1/images` | Higher quota | | Tier 2 | `GET /v1/files/:key/comments`, `GET /v1/files/:key/variables/local` | Moderate quota | | Tier 3 | `GET /v1/teams/:id/components`, `GET /v1/teams/:id/styles` | Lower quota | **429 response headers:** | Header | Type | Meaning | |--------|------|---------| | `Retry-After` | Integer (seconds) | Wait this long before retrying | | `X-Figma-Plan-Tier` | String | Your Figma plan level | | `X-Figma-Rate-Limit-Type` | String | `"low"` or `"high"` rate limit | | `X-Figma-Upgrade-Link` | String | URL to upgrade for higher limits | ### Step 2: Implement Exponential Backoff ```typescript async function figmaFetchWithRetry( path: string, token: string, maxRetries = 5 ): Promise<any> { for (let attempt = 0; attempt <= maxRetries; attempt++) { const res = await fetch(`https://api.figma.com${path}`, { headers: { 'X-Figma-Token': token }, }); if (res.status === 429) { const retryAfter = parse...